http://blogs.msdn.com/steverowe/archive/2007/03/25/ten-things-you-should-know-as-a-developer.aspxAndres Taylor gives us his top ten things he's learned about software development. The list is insightful and definitely worth reading. Here are my two favorites and my interpretation of them: It all comes down to working software - People pay you foren-USCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.msdn.com/steverowe/archive/2007/03/25/ten-things-you-should-know-as-a-developer.aspx#1955298Tue, 27 Mar 2007 00:28:06 GMT91d46819-8472-40ad-a661-2c78acb4018c:1955298Andrew<p>I agree, those are two best ones for sure. Some of the others I flat out disagree with, especially number 5. In my experience I've seen at least an order of magnitude more schedule slips caused by not doing sufficient investigation and design up front than by delaying the start of coding to iterate on the design some more. Andr&#233;s seems to equate more design time to a more complicated design, the opposite has usually been true in projects that I've been involved with!</p> <p>As Rob Short put it in his recent Channel9 video, you don't start building a house by getting somebody to nail together a bunch of 2x4s while the architect is still working on the plans, yet we seem to do this all the time in software.</p> http://blogs.msdn.com/steverowe/archive/2007/03/25/ten-things-you-should-know-as-a-developer.aspx#1955418Tue, 27 Mar 2007 01:06:16 GMT91d46819-8472-40ad-a661-2c78acb4018c:1955418SteveRowe<p>Good point. &nbsp;If you look at Andres' bio you'll see that he's heavily involved in the agile software movement. &nbsp;While Agile has a lot of good ideas, some can be taken too far. &nbsp;Not enough planning is one of those that's often taken farther than it should be.</p>