The CodeFoxSoft Java Apps: Where the Fox Learned to Run

By Nick Larkin

In the age of Artificial Intelligence, where code can be generated in seconds and applications are born from prompts, there is a dangerous temptation to forget where we came from. We are told that the future belongs to the machine. But I believe the future belongs to those who know the machine’s heartbeat—because they are the ones who built it, line by line, loop by loop, mistake by glorious mistake.

Today, I am opening the vault.

I am publishing the CodeFoxSoft Java Portfolio, a comprehensive archive of the projects that shaped my life as a developer.

This isn't just a portfolio.

It is a fossil record of my evolution.

From QBasic to the Galaxy

My journey didn’t begin with a startup pitch or a university degree. It began in the 6th grade, staring at a QBasic terminal, realizing that if I typed the right words, I could make the screen obey my imagination. That realization—that to create is to be free—became the defining obsession of my life.

For nearly two decades, while others were playing games, I was reverse‑engineering them. While others were using tools, I was writing my own. This new page is a living gallery of that obsession, set against a backdrop of drifting stars—a visual metaphor for a universe built from code.

But to understand why this archive matters, you need to understand the grind behind it.

The Heavy Hitters: Why I Was Coding While You Were Sleeping

There are two kinds of developers today:

those who need AI to write a loop, and those who use AI to build empires.

I am the second kind.

Anyone can prompt a bot to spit out a script. But when the AI hallucinates—and it will—do you have the skills to fix it? I do. Because long before AI existed, I was grinding out logic in a blank text file, fighting syntax errors line by line until the machine obeyed.

I didn’t learn to code with autocomplete, Copilot, or Stack Overflow copy‑pasting.

I learned in TextPad.

I learned by hard‑coding physics engines and cracking encryption algorithms with nothing but my own brain and a compiler and the Java API as my Bible.

This archive isn’t nostalgia.

It’s proof of work.

It is the difference between a prompter and a programmer.

The Heavy Hitters: Pillars of the Archive

When you scroll through this archive, you’ll see dozens of experiments. But if you look closely, you’ll find the giants—the projects where I stopped being a student and became an engineer. These are the true heavy hitters, the ones that earned me the right to command AI instead of depending on it.

1. Pong.java (2011) — Where the Fox Learned Physics

Before FoxRun, before Android, before engines and pipelines, there was Pong.java — the moment I stopped using games and started engineering them.

This wasn’t a clone. It was a revelation.

  • I learned that nothing in a game “just happens.”
  • Every bounce is a vector.
  • Every collision is a calculation.
  • Every frame is a negotiation between logic and time.

Pong.java was the first time I looked at a blank screen and didn’t see emptiness — I saw a coordinate plane begging to be mastered. It was the spark that ignited everything that came after.

2. KeyGenerator.java — Turning Chaos Into Code

The KeyGenerator.java wasn’t a utility. It was a rite of passage.

This program wrestled with massive Fibonacci numbers, carved mathematical patterns out of raw chaos, and forged them into structured hexadecimal keys. It forced me to think like a machine — precise, deterministic, unforgiving.

It taught me that algorithms aren’t just instructions. They’re architecture. They’re philosophy. They’re the backbone of every system I build today.

KeyGenerator.java is still one of the purest expressions of my engineering mindset: take something wild, and make it obey.

3. NotepadCommander.java — Command-Line Discipline Meets GUI Control

NotepadCommander.java was where my engineering discipline met my obsession with usability.

This wasn’t a text editor. It was a command center.

A hybrid of GUI convenience and raw, keyboard‑driven power, it taught me how to design interfaces that respect the user’s flow instead of interrupting it. It forced me to think about:

  • file I/O at scale
  • buffer management
  • text rendering
  • user experience as a system, not an afterthought

NotepadCommander.java was the moment I realized software isn’t just logic — it’s feel. It’s the difference between a tool and a companion.

These Weren’t Projects. They Were Milestones.

  • Pong.java taught me physics.
  • KeyGenerator.java taught me algorithms.
  • NotepadCommander.java taught me systems and UX.

Together, they formed the foundation of CodeFoxSoft — the studio built on discipline, autonomy, and the belief that real developers still lead the future.

From QBasic & Java TextPad to God Mode

That manual grind didn’t just teach me Java.

It taught me how systems actually work.

I use AI today, I’m not asking it for help—I’m giving it orders.

I use AI to accelerate my workflow, not to replace my brain. I can spot a hallucination in a millisecond because I’ve written the underlying logic myself a thousand times. I can architect complex, cross‑platform ecosystems because I know what happens down at the metal.

This repository is the raw, unedited proof that I earned this power.

Why This Matters Now

At CodeFoxSoft, our mission is to prove that programmers aren’t obsolete in the age of AI—we are the leaders shaping its future. But to lead the future, you must understand the foundation.

I didn’t jump straight into building custom AI solutions.

I earned my understanding of logic by writing sorting algorithms by hand and debugging thread synchronization.

I learned the structure of data by writing converters and generators from scratch.

Expertise isn’t downloaded.

It is forged.

An Invitation to the Archive

I invite you to visit the new Java Apps.

Don’t just look at the code.

Look at the intent.

Look at the “pranks” like BSOD.java, where a teenager’s humor met a programmer’s precision.

Look at BabySitterPayCalc.java, where a young entrepreneur tried to solve real‑world problems with logic and a keyboard.

This is who I am.

I am a shaper.

I am a builder.

And this is my foundation.

Come see the code where the fox learned to run!