http://blogs.msdn.com/b/coolbeans/archive/2006/12/21/risky-business.aspxYou've either experienced this first hand or heard about someone that has. You have a group project due next week and things are going great. By the assignment due date you have everything but a few small bugs worked out. You're looking at a 95%. Buten-USTelligent Evolution Platform Developer Build (Build: 5.6.50428.7875)http://blogs.msdn.com/b/coolbeans/archive/2006/12/21/risky-business.aspx#1509011Mon, 22 Jan 2007 21:01:31 GMT91d46819-8472-40ad-a661-2c78acb4018c:1509011Mike Lutz<p>Chris:</p> <p>You wrote:</p> <p>Be prepared to have someone reject a code change you make, even though it's just a trivial, easy code change and you really want to get it fixed and you don't understand how in the world the original dev didn't do it this way the first time. Whenever I find myself going down this road it's a clear sign that I don't understand why the code was written the way it was.</p> <p>This, of course, is one of the things that makes software development so exciting:</p> <p>1. The original developer may have been an idiot (this always has probability greater than zero).</p> <p>2. The original developer may have been addressing an issue that is no longer relevant (e.g., packing data tightly in bytes because memory is scarce).</p> <p>3. The original developer may have possessed a subtle insight that has escaped you.</p> <p>All of these are addressed, to some extent, but including a rationale as part of the class / component / subsystem / system documentation. Even idiots have reasons for doing the abominable work they do! Whatever the case, it would be nice to have the rationale out in the open so you have better information on which to assess the risk of change.</p> <p>Pedantically yours,</p> <p>Mike</p> <div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=1509011" width="1" height="1">http://blogs.msdn.com/b/coolbeans/archive/2006/12/21/risky-business.aspx#1435855Tue, 09 Jan 2007 01:03:47 GMT91d46819-8472-40ad-a661-2c78acb4018c:1435855CoolBeans: From College to Industry<p>Who has ever met that guy that insisted on writing every piece of code to be as fast as possible? We'll</p> <img src="http://blogs.msdn.com/aggbug.aspx?PostID=1435855" width="1" height="1">http://blogs.msdn.com/b/coolbeans/archive/2006/12/21/risky-business.aspx#1376496Fri, 29 Dec 2006 01:01:32 GMT91d46819-8472-40ad-a661-2c78acb4018c:1376496Mike Fried's Blog<p>A collection of some good posts by other Microsoft bloggers to tell a tale about quality in software development.</p> <img src="http://blogs.msdn.com/aggbug.aspx?PostID=1376496" width="1" height="1">