I either question or don't understand this. > Code Churn is the percentage of the code workflow of an engineer. It normally means the frequency of lines added

I either question or don't understand this. > Code Churn is the percentage of the code workflow of an engineer. It normally means the frequency of lines added and deleted in every commit. Measuring the churn, managers are able to control the software development process, fundamentally indicating the quality of the process of each engineer. The spikes normally represent that something is not going as normal as it should be. The whole article doesn't really feel that agile? I dunno