2,199 karma · joined March 28, 2007
Most of us hackers are jack of all trades, focusing on web design, databases, business logic, and security. It is difficult to be an expert in all areas while simultaneously focusing on speed of release. Just because a company has security experts doesn't guarantee secure software (Microsoft), but in many cases it does help.
If I work on several project concurrently, there's always one of them that I am more passionate about at any given time, causing me to think about it at nearly all hours of the day. Interestingly, the one I am more passionate about oscillates -- and is nearly always the project I have most recently worked on for a large chunk of time. Therefore, it is the one in which I am holding the most context in my head.
Basically you always want to generate ideas separately, then expand on them in a group. The reason is that a group approach from the start will squash somewhat crazy concepts before sufficient time has been put into making them practical. As a result, the most creative ideas are shot down before they are given a chance to be refined.
Instead, if you generate ideas on your own you can spend more time on a half-baked concept in order to round out its flaws. Then once its ready, other people can help provide different perspectives on the idea without shooting it down outright.
Therefore I don't see this article as simply advocating a single founder approach. However, co-founders should harden their new ideas on their own before proposing them to each other for critique.
I'll give him the benefit of the doubt, since to me it does seem reasonable that his comments were taken out of context.