| Sumario: | Getting out of tech debt can feel like a Sisyphean task. After weeks of work, the success case is to have the app working the way it used to. It's not uncommon for organizations to declare code bankruptcy and rewrite working systems from the ground up. How do we end up in this situation? How do we measure it? And how do we alleviate, or even better, prevent such a situation? Join expert Chelsea Troy to explore technical debt and its impact on an organization. You'll learn how this debt builds up, how to measure it, and how to zero in on areas of greatest need--identifying high-leverage code changes and prioritizing them over renovations. You'll also explore the skills that tech teams use to prevent and reduce tech debt so you can apply them in your own organization. What you'll learn and how you can apply it: By the end of this course, you should be able to marshal you team's morass of frustration around your technical debt into an actual plan with prioritized steps to reduce and control it. This course is for you because: You're an engineer who wants to understand and reduce tech debt. You work with engineers or manage large projects and want the code to work, and keep working, without burning out the team. Prerequisites: Experience leading technical teams or working with a code base that's becoming hard to maintain (useful but not required).
|
|---|
