> "I think not sucking is way more of an important thing to pay attention to first," Like "build something people want". One way to looks at it is in terms of

> "I think not sucking is way more of an important thing to pay attention to first," Like "build something people want". One way to looks at it is in terms of dependencies. Complicated problems have a ton of dependencies, so that when you change one thing, it ripples through, changing other things. Therefore you'd best get the most important things right first, leaving everything else loose, flexible and uncommitted, so that as you fiddle with the important things, you aren't tied down by other issues. I find I can easily become overly fond of some secondary aspect that prevents me backing out of that local minima and seeing the true (or truer) truth. Once you've got the key things right, you can start worrying about secondary things (secondary in that they are still important, just not as important). So it's similar to the knuth quote alluded to (http://c2.com/cgi/wiki?PrematureOptimization http://c2.com/cgi/wiki?PrematureOptimization). (though I'd say that the most important thing is understanding the problem and solution, rather than having correct code). It's really good to just completely forget about making money, and set out purely to make the world a better place (or realize a vision). It's freeing.