alt Hacker News> Spending 0.5% of that per year on software (development, bug-fixing, performance, and QA) would help tremendously. They’d be insurmountable.
Doesn't really help:
https://en.wikipedia.org/wiki/The_Mythical_Man-Month
Also, "bug fixing" tends to add new bugs - any kind of change can cause regressions. It's quite difficult.
Replies
FireBeyond • yesterday at 6:01 PM
This is a little simplistic. Investing more in the quality component of the org - valuable.
TM3 is basically "if this is your approach to shipping sooner / more quickly, then you're going to have a bad time." It's not a solution for a delayed project. It's not "you shouldn't invest more in the infrastructure of a large project" (or at least not blindly).
➕ show 1 reply
>Doesn't really help:
That's just a classic software development book. What makes its lessons scientific fact?
Also, it's about a singular project that's late.
Not necessarily applicable to dozens of projects with understuffed teams. Adding people to such teams to help, and assigning new people to look and fix bugs nobody cares about now because they're overworked on some "flagship" new features, is a different case.