Lessons in Software

Editor’s note: This is a guest post from Eric Brechner. Eric is author of the book, and blog, I.M. Wright’s “Hard Code.”  At Microsoft, Eric is Director of Development Excellence on the Engineering Excellence team.  His group is responsible for improving the people, process, and practices of software development across Microsoft.  Eric has more than …

Editor’s note: This is a guest post from Mike de Libero. Mike has been doing software development for more than 9 years in a variety of settings. He’s worked as a freelance developer. He’s also worked on a small team of developers maintaining 30+ programs at one time. He’s even worked as a security tester on the Microsoft Office team.

When J.D. asked me to share my thoughts on some top software development lessons I've learned throughout my time as a developer, I jumped at the chance. I have had successes and failures, and consulted with teams that share the same. Below is my list of 10 lessons I have learned through hard experience. This list is by no means definitive, but is gleaned from years of development experience.
Without further ado…

This is a guest post from Alok Srivastava on software lessons learned. Alok is a solution architect at Microsoft with more than 17 years of industry experience. He specializes in software architecture, large-scale systems, and distributed computing. Alok has filed for a dozen patents, published several papers, and presents his ideas at seveal conferences. He has a wealth of experience across large scale projects, database extensibility, multimedia and content management in RDBMS, Web services, portal technologies, and content distribution networks. In this post, Alok shares his lessons learned ...