March 2018
Intermediate to advanced
276 pages
7h 11m
English
Si vis pacem, para bellum.
There’s a common belief in our industry that technical debt sneaks into a codebase over time. However, recent research disagrees and suggests that many problematic code smells are introduced upon creation, and future evolution of the code merely continues to dig that hole deeper. This means we need a way to catch potential problems early, ideally before they enter our master branch. In this chapter we explore preventive and predictive uses of behavioral code analysis. Such analysis information becomes like an extra team member that helps us by pointing out areas of the code in need of our attention.
We start by detecting early warnings on ...