Every day I talk to many engineers and managers who want to be better. Better at developing software, better at shipping software, better at reacting to change in the marketplace, better at preserving backward compatibility, better at integrating new technologies, better at working efficiently, better at preventing and detecting bugs and errors, and so on.
I have often heard arguments that essentially say “all we need is a formal written process and things will be better”. I’ve consistently argued against that mindset, since I believe that principles are much more enduring than rules, and writing many rules often prevents people from doing the right thing.
You should all read this post from Jeff Patton why the best software design and development process is all in your head. Jeff explains so much more eloquently than I could why …
[Read more]