Summary
Getting out of tech debt can feel like a Sisyphean task. After weeks of work, the success case is for the app to work the same as it used to. Organisations often declare code bankruptcy and rewrite working systems from scratch. How do we end up here? And how do we alleviate, or even better, prevent such a situation? In this workshop, you will learn how to measure tech debt and address the areas of highest need first. You’ll learn to identify high leverage code changes and separate those from renovations. You’ll also learn about the skills tech teams can use to prevent and reduce tech debt.
Examples will be largely in Python, but the material is programming language agnostic, it is not a barrier to understanding this code.
Testimonial
I binged the entire course in a day and can't wait to do it again with [my team]. - Nate Parsons, Senior Quality Engineer at Planet
Chelsea is an excellent instructor. I learned more from this short workshop than my entire graduate course about software maintenance.
Bringing in Chelsea was some of the best money I ever spent to help my team. - Trevor Austin, CTO, Hologram.