I learned Odin

This isn't a technical review of Odin; it's a case study in developer burnout caused by shifting from creator to 'co-pilot.' The subject, a seasoned programmer, details his emotional and technical journey of rewriting a game in Odin after abandoning a messy Lua codebase. The core signal is not about language features, but about how the current AI-assisted workflow eroded his sense of agency. He frames the 'AI speed-up' as largely cosmetic for projects where he cares about the outcome, noting it forced him to 'greatly slow down' and killed his passion.

His technical observations on Odin are pragmatic: the language provides explicit function overloading, native 'using' for composition, and a 'vendor' system that bundles libraries like Raylib and Box2D as first-class citizens, removing dependency hell. This allows for a frictionless native development experience. The contrast is stark: he describes Raylib interfaces as 'so much better' than Love2D, suggesting that ergonomic, manual coding can feel faster and more comprehensible than generating opaque Lua via AI.

The key tradeoff he explores is psychological, not technical. He admits that for low-care tasks, AI provides raw speed, but for deep work, the abstraction layer introduced by AI prompting ('turn right three times to turn left') creates a sense of loss of control. This is a critical signal for engineering leaders who assume tool adoption is solely a productivity equation, ignoring developer satisfaction and code ownership.

What's missing: there are no benchmarks, no large-scale team dynamics discussed, and insights on Odin are limited to 20-30 hours of use. The claim that AI works 'just fine' with Odin is contradicted by his admission that he had to 'refactor all the code completely different.' The real story is a personal, anecdotal rejection of the AI developer persona to reclaim the 'joy of programming.'