- Photo
- —
- Name
- —
- Field
- Software engineering
- Year
- 1987
- Author(s)
- Frederick P. Brooks Jr.
- Core idea
- Some complexity in software is essential to the problem itself; tools and processes mainly chip away at accidental complexity, so there’s no single magic fix.
- Why I care
- Great reality check when someone thinks a new framework, methodology, or AI tool is going to save the release—helps you separate hard product problems from tooling drama.
- Great for
- Planning big rewrites, discussing tech debt with non‑engineers, and saying “no” to silver‑bullet vendor pitches.
- Key concept to Google
- Essential vs accidental complexity in software
- Difficulty
- Medium—short but dense; worth a slow pass.