Conceptual integrity and counting lines of code
- ID
- 15819
- Status
- summarized
- Published
- 20 Aug 2026, 6:46 AM
- Fetched
- 20 Aug 2026, 7:09 AM
- Provider
- Simon Willison
- Category
- developer-ai
- Original URL
- https://simonwillison.net/2026/Aug/19/conceptual-integrity-and-counting-lines-of-code/
- Source URL
- https://simonwillison.net/atom/everything/
Summary
- Score
- 7.5
- Created
- 20 Aug 2026, 7:09 AM
- Tags
- Audience
- developersvibe_codersai_agent_userssaas_founders
What happened
Simon Willison argues that lines of code can be a meaningful productivity metric with AI coding agents, since agents can push output from ~50-200 lines/day to ~1000 lines of debugged, tested code — but only with senior-level skill. The new bottleneck is cognitive capacity, not code generation speed, and fast agent-generated features risk destroying conceptual integrity, producing software that grows in random directions like the Winchester Mystery House.
Why it matters
If you're shipping features with coding agents, your limiting factor is now your ability to hold the system's architecture in your head, not typing speed. Treat conceptual integrity as a first-class review concern: before accepting agent-generated code, check whether it fits the existing design or adds a 'weird bump' that will confuse the next person who reads it.
Discussion angle
Where do you draw the line between letting an agent ship a feature fast and stopping to enforce architectural consistency — and what review checklist actually catches the 'Winchester Mystery House' problem before it compounds?