Every system will experience some change, whether by choice, or by accident. Every organization needs change, or they risk becoming irrelevant. As stated in the previous article. Change produces inefficiencies, so how do we manage change, within our code, our projects and our organizations.
We try to plan for change, and create rules, procedures, and standards to manage the chaotic nature of change. Try to reduce the number of unknown variables. Creating standards for adjusting to change. This comes from the idea change is not predictable, but reactions can be.
Creating procedures for making changes is a key point to being a succesful programmer. If you know when to make changes, and how to make changes. You will be one step ahead of other programmers. If you know how and when to make the switch to a new set of tools. The risk of being stuck with a unruly beta can be avoided. On the other hand if you wait to long you end up using obsolete technology.
Having policies in place help keep you moving, or keep you from getting cut by the razors edge. If you can find the sweet spot in making changes, you minimize the loss of efficiencies, by the benefits made from making the change.
Part III Dinosaurs and Lemmings
