She wanted a game like Dragon Quest 8. Not a sketch, not a toy, not a Scratch project with three sprites and a fade-out screen. A real action RPG — 3D world, combat, towns, NPCs, boss fights. So I built it. And she directed it.
Most people who saw the Show HN post probably thought: “Cute. Dad codes, kid watches, everyone claps.” That’s not what happened.
What happened is that an 11-year-old girl became the most demanding creative director I’ve ever worked with — and I’ve worked with plenty.
The most underrated skill in software isn’t engineering. It’s knowing what’s actually fun.
She didn’t write a line of code. She didn’t need to. She played. She tested. She came back with notes. “The boss fight is too easy.” “The village needs more people.” “I don’t like how she walks.”
That’s product feedback. Raw, unfiltered, and brutally honest — because she had no idea she was giving it. No stakeholder politics. No “let’s circle back on that.” Just a kid who wanted the game to be better, telling you exactly where it fell short.
The traditional parent-child creative dynamic is simple: parent decides, child participates. Parent builds the Lego set, child places the last brick and gets the photo. Parent writes the book, child gets a dedication on page three. The child is always the audience, never the author.
This project flipped that completely. She was the creative lead. I was the engineer. She said “make it feel like Dragon Quest” and I had to figure out how. She held the vision. I held the keyboard.
We treat children as audiences of our work. The magic happens when you make them the author of it.
Let’s be clear about what this took technically. A full action RPG, built from scratch, on macOS, in the style of one of the most beloved JRPG franchises ever made. This is not a weekend project. This is months of architecture, rendering, combat systems, level design, animation loops, and the seventeen iterations on a single boss fight that nobody will ever notice except the 11-year-old who said “he’s still too easy.”
But here’s what’s wild: the motivation behind all that work wasn’t a roadmap. It wasn’t a KPI. It wasn’t a sprint goal or a launch date. It was a kid saying “I want to walk through this world.”
That tension — serious technical work driven by pure play — is something the entire software industry should stop and study.
We’ve mythologized the solo grind. The 2am commit. The locked room. The “deep work” session where you emerge hollow-eyed and brilliant. We treat isolation as the price of ambition. Every productivity book, every developer memoir, every founder interview reinforces the same story: greatness is built alone, in silence, through sacrifice.
This project suggests the opposite. Ambition doesn’t require isolation. It requires the right collaborator — even if that collaborator can’t spell “polymorphism.”
The best projects aren’t born in silence. They’re born when someone you love keeps asking “is it done yet?”
For every parent reading this who has a side project gathering digital dust: the problem isn’t time. You’ve spent more hours scrolling than this game took to build. The problem is that you’re building in a vacuum. You don’t need a co-founder with a Stanford CS degree and a pitch deck. You need someone who’ll play your thing and tell you, with zero diplomacy, that the walking animation looks weird.
Children are the ultimate product managers. They have no patience for your excuses. They don’t care about your technical debt, your refactoring backlog, or your “we’ll ship it next sprint.” They care about one thing: is it fun yet?
That question — stripped of every layer of professional software development theater — is the only question that ever mattered. We just forgot to ask it because we were too busy writing JIRA tickets about it.
She’s 11 now. She’ll forget the details eventually — the bug where the NPC walked through walls, the afternoon we spent agonizing over a water shader, the boss fight that took seventeen attempts to balance. Those are my memories, not hers.
But she won’t forget that her dad took her ideas seriously enough to build them. That when she said “I want a game like Dragon Quest,” nobody said “maybe when you’re older” or “that’s too hard.” Somebody sat down and made it real.
And I won’t forget that the best thing I ever built wasn’t mine. It was ours.
Legacy isn’t what you leave behind. It’s what you build together while you’re still here.
FAQ
Q: Isn't this just a dad doing all the work and slapping his kid's name on it?
A: No. The daughter defined the vision, tested every iteration, and gave the feedback that shaped the game. In any studio, the person who says 'this isn't fun yet' and 'the boss is too easy' is called a creative director. She just didn't know she had the title.
Q: What does this mean for developers who don't have kids?
A: Find a collaborator who has zero patience for your excuses and zero interest in your technical process — someone who only cares about the end result. That person will sharpen your work faster than any peer review or sprint retrospective ever will.
Q: Is the 'solo grind is dead' take actually defensible?
A: The solo grind produces code. Collaboration produces products people actually want to use. This project shipped because a kid kept asking 'is it done yet?' — a question more motivating than any deadline a manager ever set.