10 things I learned from burning myself out with AI coding agents
- •Ars Technica editor develops 50 hobby projects using Claude Code and OpenAI tools
- •Human oversight remains essential for system architecture and high-level project management
- •Current AI agents struggle with niche domains and novel logic outside training data
Benj Edwards of Ars Technica recently shared insights from a two-month intensive experimentation phase, during which he developed over 50 software projects using Claude Code and OpenAI’s tools. His experience highlights a significant paradox: while AI coding tools dramatically lower the barrier to entry for creative software development, they often amplify the workload for the human operator rather than simply replacing them. For hobbyists and professionals alike, these tools act as force multipliers that require a human "pilot" to maintain the overarching vision. The experiments revealed that today's Large Language Models (LLMs) remain tethered to their training data, making them exceptional at modern languages like JavaScript but surprisingly brittle when tasked with niche domains like retro-computing assembly. This limitation stems from the underlying Transformer architecture, which relies on statistical associations rather than true general reasoning. When a user requests something truly novel, the model often reverts to common patterns found in its training sets, requiring the user to employ sophisticated prompt strategies to bypass these semantic traps. Furthermore, Edwards identified the "90 percent problem," where agents rapidly build flashy prototypes but struggle with the tedious final polish required for production-ready software. Because these models lack a mechanism for permanent on-the-fly learning—relying instead on a temporary context window that eventually fills up or requires compacting—they often "forget" complex debugging lessons within a single session. This confirms that while AGI remains on the horizon, the current era belongs to the "human-in-the-loop" who must manage architectural scope and mitigate the risks of rapid feature creep.