
The Mythical Man-Month
Book by Fred BrooksWikipedia
35
MENTIONS
6
EPISODES
5
PODCASTS
Search complete. 35 mentions across 6 episodes found for "The Mythical Man-Month".
Nov 18, 2026
Lessons Learned from the Browser Wars
S
1:27Scott BerkunGUEST
What I'm going to talk to you about today is actually a very difficult talk for me to do.
S
1:32Scott BerkunGUEST
When I talked to Carolyn about coming here and speaking here, I had published a book that came out, and I talked to everyone that I knew about where I could go, maybe talk about some of the things from the book.
S
1:41Scott BerkunGUEST
Carolyn and I talked, and we tried to come up with something more interesting than just telling you about, well, page 27 tells you, you know, I don't want to give you a verbatim of the book.
S
1:49Scott BerkunGUEST
So we said, well, let's talk about stuff from the browser.
S
1:51Scott BerkunGUEST
Hey, yeah, I spent a lot of time working on that.
S
2:08Scott BerkunGUEST
It's all interesting to me, my lessons, what did Scott learn.
S
2:12Scott BerkunGUEST
So I had to spend a lot of time refining this to be not just lessons that I learned, but lessons that I learned that might be interesting to other people, especially people at Google, and people who might not be old enough to remember when the browser wars, the first browser wars, took place.
S
2:27Scott BerkunGUEST
So I'm not going to talk too much about the book.
Hyperproductive Distributed Scrum Teams
J
23:18Jeff SutherlandGUEST
They've done a lot of research on this, and The surgical team was the best way at IBM to develop software.
J
23:26Jeff SutherlandGUEST
Has anybody read The Mythical Man Month? A few of you.
J
23:29Jeff SutherlandGUEST
Yeah, there's still people reading that.
J
23:31Jeff SutherlandGUEST
It's still a classic.
Law of Reversed Effort | PocketByte #64
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.
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.
P
Unknown podcast
Brooks's Law meets AI agents
Oct 27 · 1 Mention
S
0:56speaker_0UNKNOWN
Blogger Jan Vandenberg proposed today a new Brooks' law for AI agents, that adding agents to unclear requirements gets you the wrong answer faster.
S
1:05speaker_0UNKNOWN
Fred Brooks set down the original in his 1975 book, The Mythical Man-Month, and it says adding people to a late software project makes it later.
S
1:14speaker_0UNKNOWN
Vandenberg saw the law at work last weekend as four people failed to connect a laptop to a screen, and he chose not to make it five.
S
1:22speaker_0UNKNOWN
At first glance, he writes, agents should break the law because they need no onboarding, no stand-ups, and no office politics.
Henrik Kniberg: Autonomous AI Agents - Episode 425
J
36:40Jeffrey PalermoHOST
Every software engineer, every team member needs a number of personal agents.
J
36:46Jeffrey PalermoHOST
I'm reminded of Fred Brooks' surgical team essay in his Mythical Man book.
J
36:50Jeffrey PalermoHOST
Yes.
J
36:51Jeffrey PalermoHOST
Yeah, I know about that one.