Posts tagged software-engineering
-
The Mythical Man-Month: Chapters 13-End
TLDR: In the second half of The Mythical Man-Month, Brooks closes the argument around integration, milestones, documentation, no silver bullet, incremental development, and the architect role.
-
The Lego work method: simplicity is an operating discipline
TLDR: The useful lesson from Lego is not a slogan about creativity. It is an operating discipline: stay close to the customer, keep accountability internal, reduce complexity, and make execution visible.
-
The Mythical Man-Month: chapters 1-6
The first six chapters still matter in the agent-coding era because Brooks was not mainly warning about typing speed. He was warning about coordination, conceptual integrity, integration, and the cost of turning programs into systems.
-
The Mythical Man-Month, Chapters 7-12: coordination is the product
TLDR: Chapters 7-12 make one old lesson feel new again: large software fails when coordination, budgets, documents, prototypes, and tools are treated as secondary work. Agent systems inherit the same constraints.
-
The End of Software Engineering: code is becoming a runtime artifact
TLDR: The title is deliberately provocative, but the useful claim is narrower: agentic systems move durable value away from static code alone and toward intent, tools, memory, evals, observability, and governance.