The point is that Microsoft has the money to hire 100x more developers than the other guys, they should at least be well organized enough to deploy a part of that man power effectively.
Lets put it this way, there are 7 companies out there (at least) maintaining various different distributions of UNIX that can patch quickly, why can't Microsoft patch their 7 operating systems as quickly? From my view what you are saying is that because Microsoft is a monolithic company with 7 code bases it is somehow harder than 7 companies with 1 code base each? How does that track? Especially when Microsoft has a 100x more money than each of those other companies.
I'm not saying there is such a thing as a man-month. I'm saying there are ways to organize production, teams, and software so that people can provide more work than in poorly managed environments.
Flat out 'more money to fix the problem' should never make things slower. Worst case you can ignore the money.
Even if it's too late to add people for project X, you should be able to use the money for something to improve productivity on project X+3.
If I'm wrong about something please explain.
I don't know how I can my my point more clear.
If a manager shoves in more workers and slows things down, they are failing at their job.
They are worse than useless.
Because someone useless would take the extra budget, not hire anyone, and not slow down the work. Perhaps they would waste it in vegas.
I am saying nothing that contradicts that book. Just two simple points:
1. More resources only slow down a project when they are misused. They are never inherently bad.
2. It's not even hard to speed up work on security bugs, because each bugfix is a different project and can have its own dedicated team.
Please actually point out something I said that was wrong, instead of making vague references.
Ignoring more money is pretty unlikely to be an option as a whole, and inefficiencies generally cascade down to some extent.
But even more important is that these outside slowdown effects are pretty minor. If this was software development then you might have no recourse and you'd be somewhat slower overall. But this is handling many many independent projects. You can hire more teams without having man-month problems, and then handle bugs efficiently.
>Ignoring more money is pretty unlikely to be an option as a whole, and inefficiencies generally cascade down to some extent.
Again, I blame management. A nice sturdy cardboard box as a manager is impervious to social effects from other departments, and it can soak up extra cash too.
I expect anyone being paid to manage to do a better job than a box. Not to go along with the flow uncritically.
Often the size, scope and wealth of resources induces an increasingly slower response to such things.