This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
I'm looking for the name of a specific book, but for the life of me, i cannot remember the name. It's a book on design principles of programming projects, and it's written by a guy (I *THINK* it is that is) that use to work at IBM, and saw a lot of these rules broken.
The book had rules like, even if you throw more money on a project, it doesn't meant it will fix/finish the project, or other rules like more programmers does not mean a faster project completion.
Anyone know the name of this book!??! I really wanted to read it but I haven't been able to find the name of the book!
The Mythical Man-Month was written by Fred Brooks, who worked on IBM's OS/360. Brooks' Law is generally stated as "Adding manpower to a late software project makes it later" so it sounds like what you're looking for.