Get More Details with Code Churn
We covered a lot of ground in this chapter. First, we talked about the perils of fragmented development efforts. You learned about its link to post-release defects. You also learned to analyze the problem and visualize the result with fractal figures. With fractal figures, you got an overview of how the development was shared.
We then took the idea to the system level. You’ve already learned that much of our time as software developers is spent communicating. Now you’ve seen how to build a knowledge map of your codebase to help you find the correct person to discuss a particular feature or piece of code with. We also saw that these techniques go beyond programming and provide information useful to technical managers ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access