Class Central is learner-supported. When you buy through links on our site, we may earn an affiliate commission.

YouTube

Prioritizing Technical Debt Using Version Control Data

ChariotSolutions via YouTube

Start learning Write review
Coursera Ad

AI, Data Science & Cloud Certificates from Google, IBM & Meta

Learn More → University of the People Ad

Earn Your CS Degree, Tuition-Free, 100% Online!

Learn More →

Overview

Google, IBM & Meta Certificates – 40% Off
One Coursera Plus subscription covers most Professional Certificates on Coursera.
Unlock All Certificates
This course presents a language-neutral, data-informed approach to prioritizing technical debt. It uses version-control data and case studies from Android, the Linux Kernel, and .NET Core to identify code hotspots and balance maintenance with new development.

Syllabus

Intro
Lehman's "Laws" of Software Evolution
Are We Treating Symptoms Instead of the Real Issues
QUANTIFYING TECHNICAL DEBT?
THE PERILS QUANTIFYING TECHNICAL DEBT
Version-Control - A Behavioral Data Source
Case Study: Android
Actionable Insights?
Hotspots: X-Ray ActivityManager Service. Java
X-Ray of ActivityManager Service.java
Why You Don't Have To Fix All Technical Debt
Code Quality In Context: Why you shouldn't fix all code is!
What Is Legacy Code?
The Technical Debt That Wasn't
Software Evolution power laws are everywhere
Case Study: Off-Boarding
Case Study: ASP.NET MVC Core
Mitigate off-boarding risks
There's More to Code Complexity than Code
Tooling: Try it on your own Code

Taught by

ChariotSolutions

Reviews

Start your review of Prioritizing Technical Debt Using Version Control Data

Start learning

Never Stop Learning.

Get personalized course recommendations, track subjects and courses with reminders, and more.

Sign up for free
Someone learning on their laptop while sitting on the floor.