Category
How the game gets built rather than what got built: the notes, plans and habits that let an AI find its own work again.
7 posts
Five stack choices and what each one charged: a physics engine never allowed near the simulation, a renderer whose failure mode is a blank white map, and 1,266 files with no upstream maintainer.
A nine faction RTS with a campaign, built in 140 days by one human who has never read the code and one model that wrote all of it. How that actually works.
Capability pays where a change can be wrong in a way nothing would notice. Sort a week of your own work by what would catch it, and the answer is usually the effort setting rather than the model.
642,530 lines directed by someone who has never opened a file. The plan is the interface, and this is what a plan has to contain to be arguable by a reader who cannot check the code.
Parallel agents work well on separate files and fail on shared decisions. Three collisions from building this blog, and the brief shape that prevents them.
A dwarf army, a goblin fortress and the ground under both were built the same afternoon by different sessions. What that buys, and the one rule it cost to learn.
Rewriting the pathfinder under an army of wargs meant comparing 18,000 routes against the old one. That only happens if each run starts without approval.
