What's this about?
A developer's account of six months writing code only through agents. The line that took over the thread was not about AI at all: "the bigger cost was the typing. Every time I wanted to build something, I could see the code in my head. I just couldn't type it out fast enough."
Why did that line resonate so much?
Because it names a specific frustration that many programmers have never heard described: the gap between having a solution fully formed and the physical time to enter it. For some people that gap is the main source of stress in a long coding session. For others it doesn't exist at all — and the thread is largely the discovery that these are two different kinds of people who have been talking past each other for years.
What's the community saying?
HN 66 points, 98 comments — an unusually high comment-to-point ratio, which means argument
- Immediate agreement from people who describe physical tension and back pain from the mismatch between thought and typing speed.
- A worrying side effect reported by more than one person: as AI understands sloppy input, their own typing accuracy and language precision have degraded.
- The strongest dissent: the bottleneck was never typing, it was "hammock time" — thinking away from the keyboard.
- The most substantive counter-argument: typing time was *synergistic* thinking time, and writing the code out often produced a better design than the one in your head.
- The pragmatic defence of agents: it isn't about speed for its own sake, it is that a backlog of projects shelved for lack of time has finally become reachable.
- A melancholy thread about flow state — the meditative zone where ideas flow into code — and a suggestion that losing it contributes to burnout among heavy AI coders.