Code entropy

Here I'll describe an issue that comes up when we write our code. As we add more functionality, we sometimes decide to delete old one, but do so only partially. Or we write incomplete code. Or we comment it to be there just in case something goes wrong. This is how code becomes obsolete and carefully thought-out architectures start to decay.

This shows that work is done twice for every unique, interconnected technology couple. If there are many different people with fragmented responsibilities on a team, they may need common standards or an extensive and costly communication to prevent that things get out of control. At the end, the internal connections between people might start to resemble the technological ones in their nature.

This should be a reminder for us to change our associations as we change our code to minimize the quality decrease in our system.

bit.ly/12wHIEQ