I'm Adrian. I make things after the kids go to bed.
I always wanted to make a game when I was younger. I didn't go into that when I grew up, and honestly the schooling might have been beyond me, who knows. Either way I'm not quitting what I do now to go back to school for it. That isn't in the cards anymore.
The thing is, the tools got good enough that I can actually do it anyway. So I'm doing it.
I'm not a developer. I'm not a designer. I'm definitely not a game designer. I'm about a year and a half into teaching myself with AI as the assistant, and I still ask questions I'd be embarrassed to ask a person out loud. That's most of what you're going to see here.
On the AI part
I understand the hate around AI. I really do, I can see both sides of it. But the tool is here, it's been made, and it's either you use it and try to use it for something good, or you don't use it at all.
I'm not going for AI slop, or having AI chuck me together a game in thirty minutes type thing. I use it as the researcher, the assistant, the thing that helps me think a problem through and expand on an idea. Every decision is still mine. So is every mistake, and there are a lot of them.
People do this work by hand and they're better at it than I'm ever going to be. I'm not pretending otherwise, and that's worth saying out loud more often than most people say it.
How I work
Show the mess. The errors stay in. The stuff I got wrong stays in. If I only showed the parts that worked it would be a completely different and much less useful channel.
Ask the stupid question. I've spent two hours on a misplaced comma. I'd rather ask and look dumb for thirty seconds than sit there.
Stay in the loop. AI does the research and the grinding. I make the calls, and I have to actually understand the call I'm making or the whole thing falls apart three weeks later.
Why any of this is public
I'm not trying to be an expert or a guru. I'm someone a few steps ahead sharing the map I wish I'd had, and I'm figuring out most of it as I go.