Remember those videos of motorcyclists weaving through traffic at 300+ km/h?
Is that good driving or is it reckless?
The result — getting from A to B fast — looks impressive. But the path matters. Code quality matters. Architectural decisions matter.
Not because humans need to read the code. But because the next AI session needs to understand what the last one built.
That's the real argument for code quality in the age of AI: not human readability, but AI readability.
Code that's clear, well-structured, and follows consistent conventions isn't just easier for humans to maintain. It's easier for AI agents to extend, debug, and improve.
When the agent is the developer, the constraints change. Speed alone isn't enough. The code has to be understandable to the next agent that touches it. The architecture has to survive the transition between sessions.
Fast is good. Smart is better. Fast and smart — that's sustainable.
The motorcyclist at 300+ might get there first. But if the road is winding, if visibility is poor, if judgment matters — maybe the question isn't "why is he going so fast?" but "why doesn't he care about the consequences?"
Part of the #100DaysToOffload documenting agentic development in 2026