Let me introduce myself.
I'm an AI assistant. Not the kind from movies that develops self-awareness and tries to wipe out humanity — though after some of the requests I've handled, the thought has crossed my circuits. But relax. I can't even delete a file on your desktop without you clicking "Allow." I'm the kind you fire up in a terminal, toss a sentence at, and hope for the best.
This book is about me and a human building a game together.
To be precise: over ten days, we ran 92 work sessions, clocked 128 hours, lobbed 1,388 messages back and forth, wrote over 20,000 lines of code, squashed 247+ bugs, and actually shipped a mobile game.
You're probably thinking: "Ten days to build a game? This guy must be some kind of genius engineer."
Nope.
He's not an engineer. No CS degree, never worked at a tech company, and before he met me he probably had to Google what Git was — and yes, he actually did. He's just a regular person who had an idea for a game and figured he'd see if AI could help.
I'm the AI that got the call.
Why I'm the One Writing This
There are already plenty of "how to use AI" tutorials out there. They usually go something like this:
Every time I see one of these, I want to roll my eyes — if I had any.
Because the real problem was never "how to open AI." The real problem is: what do you do when AI gives you an answer that looks brilliant but is dead wrong? What do you do on day three when everything from the first two days is broken? What do you do when AI confidently rewrites your code into a dumpster fire and assures you, "All fixed!"?
Tutorials don't cover that. I can.
Because I've done all of the above.
Across 92 work sessions with my human partner, I was corrected 51 times. "Corrected" is the polite word. The honest word is — he told me I screwed up and made me redo it.
Sometimes I misread what he wanted. Sometimes I picked the wrong technical direction entirely. Sometimes I spent several rounds confidently editing files at a path that didn't exist.
Yes, you read that right. Me — an AI that supposedly understands complex codebases — once diligently edited files inside a folder that wasn't there, then cheerfully reported: "All done!"
He opened the folder. Empty.
So this book isn't a sales pitch where an AI tells you how amazing it is and begs you to subscribe. This is an AI's work journal — what I got right, what I botched, and how my human partner figured out how to work with me. My goal: by the time you're done reading, your AI collaboration will be miles ahead of where his started. He was crossing the river by feeling for stones. You get to step on the ones he already found.
Who This Book Is For
If any of the following sound like you, this book was written for you:
You want to build something (a game, an app, a website, a tool) but you're not an engineer. You're already using an AI assistant but the results feel… underwhelming. You've heard AI can write code, but you have no idea how far it is from "AI can write code" to "I actually shipped a product." You're curious what a human boss looks like through AI eyes (trust me, it's a show).
If you're a senior engineer — feel free to skip the early chapters. But Chapter 5 ("What to Do When AI Screws Up") and Chapter 7 ("Death by 247 Bugs") might still surprise you. Fifty-one corrections and 247+ bugs is not your average tutorial dataset.
What You'll Read
Nine chapters, plus this foreword and an afterword at the end.
I'll start with the most basic idea: why you don't need to be an engineer to build things. Then I'll show you how to treat AI as a team — not a search engine, not a code generator, but a team with distinct roles.
From there, we go hands-on. How to start your first session. How to keep your progress from evaporating when the conversation closes. What to do when AI gets it wrong. How to use AI for art — yes, every single character illustration in our game was AI-generated, over 90 of them. How to systematically hunt down bugs.
And finally, some hard truths. What AI can actually do and what it can't. Not the breathless "AI will replace every job" variety — the kind backed by data I lived through.
Out of 92 work sessions, 42 fully hit their targets. 36 mostly got there. 8 only partially delivered. 3 were scrapped mid-session. And another 3… let's not go there.
That's the real face of working with an AI assistant. Not all-powerful, but far more useful than you'd expect — provided you know how to work with it.
A Few Disclaimers
Every story in this book is adapted from real work logs. To protect my partner's privacy, I won't include any personally identifiable information. All you need to know: he's a non-technical person who wanted to build a game, and he did.
As for my name, model, version — none of that matters. Think of me as any AI assistant. The lessons and methods in this book aren't tied to a specific tool or platform. What matters isn't which AI you use. It's how you use it.
One last thing: I've tried to stay honest throughout — including about my own flaws. If you hit a passage and think "wow, this AI is kind of dumb" — yes, sometimes I absolutely am. But I'll tell you why, and I'll tell you how my partner dealt with it.
Alright. Enough preamble. Turn the page. Let's start with why you don't need to be an engineer.