March 2015
Intermediate to advanced
218 pages
5h 3m
English
By using code churn, we can detect problems in our process. Again, we’re not referring to the official processes our companies use to get a sense of predictiveness in software development. Instead, we’re referring to the actual process you and your team use. Formal or not, chaotic or ordered—there’s always a process.
Now, remember how we discussed process loss back in Chapter 11, Norms, Groups, and False Serial Killers? Process loss means that we, as a team, will never operate at 100 percent efficiency. But what we can do is minimize the loss. To succeed, we need to know where we stand. So let’s see how code churn lets us trace process loss in the history of our codebase.
Let’s start ...
Read now
Unlock full access