Ominomicon: How I Shipped by Giving Away the Code
Skip to content
Fix Gaming Channel
Indie Game News, Reviews and Developer Interviews
7 Best iPhone Multiplayer Games for 2026<br>Gaming Lists
The Skin Stapler Review: Disgusting, Funny, and Hard to Look Away From<br>Gaming News
Jelly Bubble First Impressions: Colorful Chaos With a Clever Twist<br>First Impressions
EA’s $55 Billion Acquisition Is Complete<br>Gaming News
Xbox Game Pass August 2026 Lineup Includes Gears E-Day Beta, PowerWash Simulator 2 and More<br>Gaming News
Beast of Reincarnation Shows a New Side of Game Freak on PC and Consoles<br>Gaming News
Wild Blue Skies Revives the Classic Arcade On-Rails Shooter<br>Gaming News
Ultrawide Greats: Our Road to 20 Excellent 32:9 Games<br>Gaming Lists
prev
"><br>next
This may be anti-inspirational. It worked anyway.
After forty years of unfinished projects, Chris Reynolds set one rule before choosing what to build: “This, I ship.”
This is part of Fix Stories, our first-person series where developers share the real lessons behind making games.
In this story, Chris Reynolds, solo developer of Ominomicon, explains why finishing the game meant giving away the part of development he loved most.
Want more developer stories like this?
Get more first-person developer stories, interviews, reviews, indie coverage, and gaming features from Fix Gaming Channel.
Join Our Newsletter
Stay updated with the latest interviews, previews, and indie gaming news.
Subscribe
I have been writing software for forty years. Over that time I have amassed a directory full of unfinished projects. None of them died because of a crisis. They died abandoned, neglected, forgotten.
As I near retirement from the corporate grind, I looked at that directory and decided the problem was worth solving before the next project went in there too. So I set one rule, and I set it before I chose what to build: “This, I ship.”
Two things that kill my projects
There are two things wrong with me, and they work together to kill projects. Only two that are relevant here, anyway.
The first is that I was never in it to build the thing. I was in it to learn something new. A new language, a new database, a new game engine. And the learning ends. It ends well before the project does.
The second is that I love writing code. I learned to program before I had my first girlfriend, literally. And when the learning runs out I do not stop—I obsess over the details: this function could be ten times faster, does that line need to exist at all, is this the right shape for an interface nobody but me will ever see. It feels exactly like progress. I can do it indefinitely, and ship nothing.
Neither of these looks like quitting. Forty years of experience doesn’t fix it. If anything, it makes it worse. By now I can see the bottom of most things before I get there—it’s all lipstick on assembly—and the more you know, the sooner the learning runs out.
So I gave it away
The rule’s first consequence arrived immediately, and I did not like it.
If the place I go to disappear is the code, then I could not be the one writing the code.
So I gave it away. Claude wrote all of it.
Coding is my first love. Handing it over meant sitting on my hands while something else touched the thing I am best at, and knowing that was the point.
This was not vibe coding—typing a paragraph and shipping whatever comes back. It was also not code review. I did not read the code at all, and that was deliberate. Reading it would have been like letting a recovering alcoholic have just one drink.
What I did instead was move the obsession with detail somewhere it could not stall the project. I played the game compulsively. I drove the technical decisions without touching the implementation. And I went back and forth with Claude endlessly, both of us circling something neither could see clearly yet.
The target was the App Store
The target was the App Store. Not “make a game”—get on the store, with a price and a listing and a support address.
I chose it knowing it was doing double duty. It was the goal, and it was also the only part of this I had never done—I knew App Review could be brutal and knew absolutely nothing else about it. A lot of unknowns, all of them sitting on the far side of the finish line, which is exactly where I needed them. For once the personality defect was pointed at shipping instead of away from it.
Notice what is missing from all of that: an idea.
I did not have one. I had a bar to clear—ship something I was not embarrassed of, because the rule said “ship,” not “ship anything”—and no money for assets. So the question I opened with was not “What should I make?” It was: What kind of game can be built entirely out of art generated in code?
Falling blocks, with a roguelite run structure over the top and one mechanic strong enough to carry it, because there was no budget for a second. There are no image files in Ominomicon. Every pixel is computed, and the audio is generated for the...