A r/gamedev thread documents how a mobile game studio switched to AI coding in the last 2-3 months, with corroborating anecdotes from developers at other companies. The picture isn’t a clean productivity leap — it’s a messy, uneven transition where the bottlenecks just move.
What the thread reports from inside studios:
- All code is written by Claude or Codex; humans only verify validity. Development hires are frozen, but existing staff face 5x-10x productivity expectations.
- Game designers must now build their own working prototypes (usually in JS) before approaching programmers for a soft launch build.
- Every paid service subscription is being evaluated for a quick homemade AI replacement — spawning one-off tools in random languages that create integration headaches for backend teams.
- Managers see one success story (a week-long task done in 2 hours) and extrapolate it to all tasks, ignoring that the real bottlenecks are testing and requirement formulation, not coding speed.
- Experienced developers still outperform juniors by a wide margin with AI tools; architecture and design decisions require human judgment and guardrails.
The sharpest observation in the thread: AI coding doesn’t remove the hard parts of software development — it moves them. When code becomes cheap to produce, validation becomes the scarce resource. And when everyone can generate their own utilities, you get integration chaos instead of productivity.
A useful, grounded snapshot of what AI coding actually looks like inside a studio right now — the hype and the friction in one thread.