In software you can't really add people and expect to get more done, because their ability to understand the program and what's going on it would require so much investment and all their work would require so much review that... ...
If you think you're a really good programmer... read Knuth's Art of Computer Programming... You should definitely send me a resume if you can read the whole thing.
Certain teams are more careful in what they write. They generate less bugs. You can know that but it still doesn't mean there might be there might not be one bug that would be bad to ship the product with.
You don't go to other books and take little pieces because although say a romantic scene may have been many times before all the details of who it is, where it is, are so intertwined in that text that it's... ...
In programming when you're making a change you have to know all the affected places, and you have to be able to model in your head what the performance impact will be.
Good developers like seeing their products sell in large quantities. They enjoy the competition of doing a better job than the other company, especially if the other company has more people on the project and they're entrenched and people are... ...
Even when I wrote Basic myself the day before I burned it into a computer I wasn't making design changes. I didn't have a testing team. I did all the testing myself. And there was no project methodology or schedule... ...
