Mythical Man Month
Summary
Martin Fowler reflects on Fred Brooks’s seminal 1975 book The Mythical Man-Month, highlighting enduring lessons like Brooks’s Law and the critical importance of conceptual integrity in software system design.
View Cached Full Text
Cached at: 05/09/26, 03:31 AM
Similar Articles
Martin Fowler: Technical, Cognitive, and Intent Debt
Martin Fowler reflects on AI’s impact on code quality, emphasizing that human laziness drives crisp abstractions while LLMs risk bloating systems with unnecessary complexity.
@Dan_Jeffries1: Finally a semi-useful read on Mythos that is free of myth and talks about what this means more practically (not this is…
Dan Jeffries comments on Cloudflare's testing of Anthropic's Mythos, arguing that the real conversation should focus on practical security improvements against AI-powered attacks, and that AI will ultimately make software more secure if teams adapt their workflows.
Tim Davis – Probabilistic engineering and the 24-7 employee
Tim Davis, head of Modular, shares his experience building an autonomous code-writing system called Compound Loop and argues that software development is shifting from deterministic to probabilistic systems, with AI agents enabling a '24-7 employee' model where human operators coordinate rather than type, while roles are splitting between high-leverage positions and lower-value agent-wrangling work.
@GergelyOrosz: How have the fundamentals of building large, distributed software systems changed the last decade? A conversation with …
Martin Kleppmann discusses how the fundamentals of building large, distributed systems have evolved over the past decade in light of the updated second edition of his book "Designing Data-Intensive Applications."
@dabit3: Nice little reference: 56 laws of software engineering. Especially great for juniors (worth bookmarking), and I also le…
A curated list of 56 software engineering laws aimed at junior developers, available at lawsofsoftwareengineering.com.