Chapter 4. Automated Code Remediation in Action
Now that we’ve covered the background for automated code remediation, we want to share some real-world case studies exploring the practice. You’ll see what leads organizations to automate code remediation and its impact on the way they work.
Case Study: Improved Developer Productivity
Our first case study takes us back to the problem of technical debt. A midsize insurance company, with over 20 million lines of code across 1,200 repositories, was struggling to close code maintenance stories without impacting the development team’s productivity. Their code maintenance work, which covered vulnerability patching, code migration, and dependency upgrades, was folded under technical debt in their systems.
The organization was averaging one large maintenance project per quarter, and each of those projects could consume the entire development team. For example, in Q2 the team had to prioritize a Spring Boot version upgrade to secure their code from the Spring4Shell vulnerability. This became 32 different stories for the development team—one per repository. It also required one developer per repository acting as the “migration expert” for the update. It was all-consuming and reduced their business output, as you can see in the Q2 results shown in Figure 4-1.
Then they started using automated code remediation with Moderne. Instead of a whole development team touching multiple repositories to maintain code, a single developer in less than a ...
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