Software Management Lessons from the 1960s
summary
Fred Brooks and The Mythical Man-Month get rechecked against System/360 history: IBM’s architecture decision creates the 8‑bit byte and a decade‑long product line, and Brooks’ concrete claims stand — Brooks’ law: adding people to a late project makes it later, estimates: prototype ≈×3 to shipable, full product ≈×9, and a practical staffing heuristic of swimlanes + 1 developers. Reuse (open source) cuts work, unit testing and top‑down design with iterative implementation actually reduce surprises, and conceptual integrity proves the biggest multiplier for usability and maintainability.
AI-written summary · about
chapters (5)
- 0:00Start
- 8:40Tasks are not parallelizable
- 18:33How fast can you code?
- 24:57Top-down design
- 26:41Design top-down, implement iteratively
related talks
44mSoftware Management Lessons from the 1960s
55mSoftware Management Lessons from the 1960s
01h 01mLessons from a lifetime of doing, teaching, managing, and leading technical development
32mMake the Right Thing the Easy Thing: Designing Processes Teams Will Actually Follow
52mSoftware Engineering : Greatest Hits 1947 2047
01h 01mInterview with Alan Kay
08mLightning talks – 101 Things Software Never Learnt
50mTactics and strategies on software development: how to reach ...