Well, while I don't think perfectionism is always a bad thing and releasing 'any old thing' as quickly as possible it's always a good idea, I definitely see whe

Well, while I don't think perfectionism is always a bad thing and releasing 'any old thing' as quickly as possible it's always a good idea, I definitely see where he's coming from. There's a balance you have to strike here between 'done quickly' and 'done perfectly', and pushing towards either end can doom your project. I mean, look at Duke Nukem Forever. The game spent 15 years in development because the creators were never happy with it, constantly felt it needed to be better than the competition and always fretted about what engine might be the 'best possible choice' for the title. That wasted millions of dollars, years of people's lives and all manner of resources for a game that would have been better released after three or four years with a couple of sequels down the line. And lots of non game examples exist there too. I'm sure you can name amazing systems that took so in development due to 'doing everything properly no matter the cost' that their nimbler competitors ate them for lunch. At the same time, you can also likely remember many examples where products got released without enough care and attention put into the coding site (or quality control in general) and it just slaughtered their reputation and long term popularity. It's a fine line you have to wander, and one that can sink a product or service if you go too far off track.