Fred Brooks: Why Adding People Makes Late Projects Later

In the 1970s, one man proved that the maddening experience of a late project slowing down after you add more people isn't bad luck. It's an inescapable law of human nature, and it still rules software today.This episode explores Fred Brooks, the computer scientist who bridged hardware engineering and human project management. From coining the term "computer architecture" to writing Brooks's Law, it reveals how a Turing Award winner understood that machines are only ever as effective as the flawed people building them.His work on early supercomputers including the IBM Stretch and the NSA's Harvest machineHow the System/360 separated hardware from architecture so software could survive upgradesWhy he called enabling lowercase letters via the 8-bit byte his single most important decisionThe communication-channel math behind Brooks's Law, born from the OS/360 nightmareHis "No Silver Bullet" argument distinguishing the accidents of software from its essence