With coding agents collapsing implementation cost, the real bottleneck shifts to shared context, precise specs, and organizational coherence.
Key Takeaways
Brooks’ Law still applies: agents amplify individual output but don’t solve the negotiation and alignment work that is the actual substance of software.
The new rate-limit is spec production: teams with agents wait on well-formed tickets and acceptance criteria, not on engineers writing code.
Jevons Paradox applies to code: cheaper code generation expands scope rather than reducing effort, making focus (saying no) harder and more critical.
Agents cannot do osmosis; whatever context isn’t explicitly packed into the prompt, file tree, or instructions is effectively missing from their reasoning.
.txt is building context-extraction agents that crawl PRs, issues, commits, and threads to externalize implicit organizational knowledge into a readable substrate for other agents.
Hacker News Comment Review
Minimal discussion so far; one commenter pointed to a related piece (“Mythical Agent Month”) extending Brooks’ Mythical Man Month framing directly to agent-era software teams.
