Screenshot of the current game with some of the code describing the pallet
Earlier this year, I was on parental leave as the tech industry changed rapidly. I was watching from afar as I rocked our baby to sleep, seeing every hot take that programming was dead.
To not fall behind too much, I spun up a side project to see how much I could get out of Opus 4.6 doing 99% of my programming.
I wrote about it, in case you want to see that journey.
I got my reps in and came away thinking “this was powerful, but I’m still a necessary piece of this process.”
Then Opus 5.5 came out, and leapfrogged my whole process.
Reimagining my game
A quick disclaimer, since I know AI is flooding the indie game space and there is a lot of pushback from gamers as slop floods the marketplace: I have no intention of…
While not being a programmer or gamer, this report is very impressive to me. What I focused on was the working relationship, the development of your prompting strategy, and the model's alignment vs mistakes.
The 150 automated playtests are the real headline here. We're moving from "AI that writes code" to "AI that actually plays, QAs, and balances the game."
It makes total sense that less prompting was required. As models get better, prompting shifts…
