Skip to main content
Fred Brooks

Fred Brooks

American software engineer and computer scientistWikipedia

Search complete. 25 mentions across 15 episodes found for "Fred Brooks".

Nov 18, 2026

Scott BerkunGUEST
28:43
Once you get to 30 smart people, 50 smart people, gets more complicated.
Scott BerkunGUEST
28:49
Fred Brooks, in his book, Mythical Man Month, has this thing called Brooks' Law that says every time you add a person to a team, the total number of people, total number of links in the network of communication goes up, not arithmetically, but geometrically.
Scott BerkunGUEST
29:04
So every person you add starts this network gets bigger and bigger.
Scott BerkunGUEST
29:09
So if you're not paying attention to how your team has changed, you have people who are still behaving as if they're a local, simple little unit, when really they're in this larger system that is demanding a different way, a different style of communication from them.
Jeff SutherlandGUEST
23:32
As good as the day it was written.
Jeff SutherlandGUEST
23:34
Fred Brooks, who ran the IBM 360 operating system, wrote it.
Jeff SutherlandGUEST
23:39
He had hundreds of developers, and he learns a lot of painful lessons.
Jeff SutherlandGUEST
23:43
And in the middle of that book, there's a chapter on the surgical team.
speaker_0NARRATOR
0:20
Welcome to the show.
Francesco GadaletaHOST
0:23
You know what's funny? That 50 years ago, a guy named Fred Brooks wrote a book about why throwing more people at a late software project makes it later.
Francesco GadaletaHOST
0:35
And he called it the mythical man month, a very famous book in the world of IT.
Francesco GadaletaHOST
0:41
It became definitely in the 80s and in the 90s.
Francesco GadaletaHOST
3:29
Now, I started writing essays, not really a book, just essays.
Francesco GadaletaHOST
3:34
They were scattered notes, really, because I kept saying, you know, the same things about AI.
Francesco GadaletaHOST
3:42
And also, I kept seeing the same pattern in teams, in Slack channels, in LinkedIn posts, you know, people budgeting AI coding assistance pretty much the way Fred Brooks, 1970s IBM managers budgeted headcount.
Francesco GadaletaHOST
4:00
you know, just add more tokens, just let the agent run longer, just buy more, you know, bigger machines, more RAM, bigger GPUs, just give it a bigger context window and it will figure it out, right? We are very familiar now with this concept you know, conclusions about computation and intelligence, as if intelligence, you know, artificial or otherwise, scaled the way a spreadsheet formula does.
speaker_4HOST
5:11
Just like attempting to force a state of calm creates anxiety, forcing an organization to hit a specific metric destroys the organic ecosystem that allowed that metric to be meaningful in the first place.
speaker_4HOST
5:23
Moving into social systems and corporate management, we find Brooks' Law.
speaker_4HOST
5:27
Famously articulated by software engineer Fred Brooks in his book, The Mythical Man-Month, Brooks observed that adding manpower to a late software project only makes it later.
speaker_4HOST
5:38
When a project hits friction or falls behind schedule, the immediate and instinctual response of leadership is to throw more raw force at the problem.
speaker_4HOST
5:49
More people, more capital, and more overhead.
Dave BradyPANELIST
14:03
You join a team or adding people, adding people to a late project makes it later.
Dave BradyPANELIST
14:06
Fred Brooks.
Dave BradyPANELIST
14:07
Right.
Dave BradyPANELIST
14:08
I've always thought of that as like, oh, you've got to ramp up on technical debt.
Kris JenkinsHOST
6:28
because I think you're alluding to a paper called Out of the Tar Pit here.
Cameron BarréGUEST
6:33
Yeah, Out of the Tar Pit, or even Fred Brooks' Mythical Man Month.
Cameron BarréGUEST
6:37
These are both places where this idea of incidental or accidental and essential complexity are kind of introduced to people.
Cameron BarréGUEST
6:47
Define them for me, because not everyone will know these terms.
Jameson LoppGUEST
7:33
And, you know, even the various methodologies for doing software engineering have vastly changed.
Jameson LoppGUEST
7:41
You know, there's actually a sort of seminal book in computer engineering by Fred Brooks where he talked about the mythical man month.
Jameson LoppGUEST
7:53
And that was basically his experience of helping build, I think, one of the first major processors and architecting one of the first major computers back then and how he realized that just bringing more people onto a software development team would actually slow down the process.
Jameson LoppGUEST
8:15
And and over the years, as various techniques and of course, network technology came along, we ended up having a plethora of different models come out for like how you collaborate with people.
Martin CasadoGUEST
38:22
And it has to come with organizational communication, which is one of the conclusions.
Martin CasadoGUEST
38:25
But the takeaway for those that are listening is that this comes from, I think, Fred Brooks, right? And like the 70s, which is basically like you had these software projects and you wanted to get them out faster.
Martin CasadoGUEST
38:35
And so they would throw more people out and then they would go slower.
Martin CasadoGUEST
38:38
Engineering has always been this bottleneck.
Peter NeumannGUEST
36:55
Maybe, yeah.
Peter NeumannGUEST
36:57
And Fred Brooks always said, build one and to throw it away so you can learn something from it.
speaker_11UNKNOWN
37:02
But the problem is that we don't learn from our mistakes.
Peter NeumannGUEST
37:06
Some of us do.
speaker_0NARRATOR
12:22
Daniel Stenberg, who leads Curl, started banning people who submitted AI slop bug reports in May 2025, writing that the project was effectively being DDoSed.
speaker_0NARRATOR
12:33
in january 2026 curl shut down its bug bounty interactive figure on hrih see bar sizes are illustrative not measured the 2026 shape follows farrow's eyes numbers above the 2031 one is my guess switch between the years to see where work waits fred brooks saw a version of this coming in 1986 In No Silver Bullet, he split the difficulties of software into two piles, borrowing Aristotle's words, essence and accidents.
speaker_0NARRATOR
13:04
The accidents are the trouble our tools cause us, like syntax, boilerplate and fighting the build.
speaker_0NARRATOR
13:09
The essence is what he called, the specification, design, and testing of this conceptual construct, which is a fancy way of saying, working out what the thing should do.

5 more episodes mention Fred Brooks.

Create an account to see the whole feed, search across every transcript, and follow the entities you care about.

We value your privacy

We use cookies to understand how you use our platform and to improve your experience. Click “Accept All” to consent, or “Decline non-essential” to opt out of non-essential cookies. Read our Privacy Policy.