Table of Contents for

Your Code as a Crime Scene

Find Your Own Hotspots

In this chapter, you learned the theory behind hotspot analyses. You learned that to identify the parts that matter for your productivity, it isn’t enough to look at a static snapshot of the code. Instead, you need to also look at where you spend most of your efforts.

We’ve now come full circle: we have a geography of code with a probability surface that lets you track down offending code. We’ll explore this concept in more detail in the next chapter, and you’ll learn to extract the information from version-control systems. It will be data that helps you find potential suspects, such as code smells and team-productivity bottlenecks.

Turn the page, and let’s walk through your first offender profile.