Tooling

One technique I keep returning to is improving a small, well-tested piece of code over a metric, in many small autonomous passes, with the worst attempts thrown away. The unit of work is one cycle: an isolated git worktree, an open-ended prompt, automatic tests, an automatic merge or discard. No single cycle is dramatic. The whole point is that they compound. It works when two things are true: the code under improvement is well tested, and the metric you care about is honestly definable. It does not work otherwise — the gate becomes either meaningless (no tests) or gameable (the wrong metric). ...

If I wanted to vibe-code a game, which game engine should I choose? Which game engine is the best for vibe coding? Unity The first engine that came to mind was Unity. I know C#, it is popular, there are a lot of resources to learn from, and in general it is indie-friendly. On the other hand, Unity has a track record of bad behavior toward the community and controversial licensing decisions. The most obvious example is the Runtime Fee controversy: Unity introduced a per-install fee in 2023, then cancelled it in 2024 after strong backlash from the developer community.1 ...