
Fred Brooks
American software engineer and computer scientistWikipedia
25
MENTIONS
15
EPISODES
14
PODCASTS
Search complete. 25 mentions across 15 episodes found for "Fred Brooks".
Nov 18, 2026
Lessons Learned from the Browser Wars
S
28:43Scott BerkunGUEST
Once you get to 30 smart people, 50 smart people, gets more complicated.
S
28:49Scott BerkunGUEST
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.
S
29:04Scott BerkunGUEST
So every person you add starts this network gets bigger and bigger.
S
29:09Scott BerkunGUEST
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.
Hyperproductive Distributed Scrum Teams
J
23:32Jeff SutherlandGUEST
As good as the day it was written.
J
23:34Jeff SutherlandGUEST
Fred Brooks, who ran the IBM 360 operating system, wrote it.
J
23:39Jeff SutherlandGUEST
He had hundreds of developers, and he learns a lot of painful lessons.
J
23:43Jeff SutherlandGUEST
And in the middle of that book, there's a chapter on the surgical team.
AI coding agents have a Mythical Man-Month problem (Ep. 322) [RB]
S
0:20speaker_0NARRATOR
Welcome to the show.
F
0:23Francesco GadaletaHOST
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.
F
0:35Francesco GadaletaHOST
And he called it the mythical man month, a very famous book in the world of IT.
F
0:41Francesco GadaletaHOST
It became definitely in the 80s and in the 90s.
F
3:29Francesco GadaletaHOST
Now, I started writing essays, not really a book, just essays.
F
3:34Francesco GadaletaHOST
They were scattered notes, really, because I kept saying, you know, the same things about AI.
F
3:42Francesco GadaletaHOST
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.
F
4:00Francesco GadaletaHOST
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.
Law of Reversed Effort | PocketByte #64
S
5:11speaker_4HOST
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.
S
5:23speaker_4HOST
Moving into social systems and corporate management, we find Brooks' Law.
S
5:27speaker_4HOST
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.
S
5:38speaker_4HOST
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.
S
5:49speaker_4HOST
More people, more capital, and more overhead.
Episode 111: The Hidden Work
D
14:03Dave BradyPANELIST
You join a team or adding people, adding people to a late project makes it later.
D
14:06Dave BradyPANELIST
Fred Brooks.
D
14:07Dave BradyPANELIST
Right.
D
14:08Dave BradyPANELIST
I've always thought of that as like, oh, you've got to ramp up on technical debt.
Why Lisp Thrives In The Age Of AI (with Cameron Barré)
K
6:28Kris JenkinsHOST
because I think you're alluding to a paper called Out of the Tar Pit here.
C
6:33Cameron BarréGUEST
Yeah, Out of the Tar Pit, or even Fred Brooks' Mythical Man Month.
C
6:37Cameron BarréGUEST
These are both places where this idea of incidental or accidental and essential complexity are kind of introduced to people.
C
6:47Cameron BarréGUEST
Define them for me, because not everyone will know these terms.
"The Safest Way To Use A Computer Is To Never Turn It On" | Jameson Lopp
J
7:33Jameson LoppGUEST
And, you know, even the various methodologies for doing software engineering have vastly changed.
J
7:41Jameson LoppGUEST
You know, there's actually a sort of seminal book in computer engineering by Fred Brooks where he talked about the mythical man month.
J
7:53Jameson LoppGUEST
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.
J
8:15Jameson LoppGUEST
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 Casado on Frontier Model Economics, AI's Slowdown, and the Cursor Deal - [Invest Like the Best, EP.498]
M
38:22Martin CasadoGUEST
And it has to come with organizational communication, which is one of the conclusions.
M
38:25Martin CasadoGUEST
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.
M
38:35Martin CasadoGUEST
And so they would throw more people out and then they would go slower.
M
38:38Martin CasadoGUEST
Engineering has always been this bottleneck.
Stanford Seminar - Tales from the Risks Forum
P
36:55Peter NeumannGUEST
Maybe, yeah.
P
36:57Peter NeumannGUEST
And Fred Brooks always said, build one and to throw it away so you can learn something from it.
S
37:02speaker_11UNKNOWN
But the problem is that we don't learn from our mistakes.
P
37:06Peter NeumannGUEST
Some of us do.
Programming Has Been Dying Since 1954. AI Might Finally Change It.
S
12:22speaker_0NARRATOR
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.
S
12:33speaker_0NARRATOR
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.
S
13:04speaker_0NARRATOR
The accidents are the trouble our tools cause us, like syntax, boilerplate and fighting the build.
S
13:09speaker_0NARRATOR
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.