Prioritizing Technical Debt as if Time and Money Matters

Prioritizing Technical Debt as if Time and Money Matters

GOTO Conferences via YouTube Direct link

Intro

1 of 18

1 of 18

Intro

Class Central Classrooms beta

YouTube videos curated by Class Central.

Classroom Contents

Prioritizing Technical Debt as if Time and Money Matters

Automatically move to the next video in the Classroom when playback concludes

  1. 1 Intro
  2. 2 Lehman's "Laws" of Software Evolution
  3. 3 QUANTIFYING TECHNICAL DEBT?
  4. 4 THE PERILS QUANTIFYING TECHNICAL DEBT
  5. 5 Version-Control - A Behavioral Data Source
  6. 6 Case Study: Android
  7. 7 X-Ray of ActivityManager Service.java
  8. 8 Code Quality In Context: Why you shouldn't fix all code issues
  9. 9 What Is Legacy Code?
  10. 10 Case Study: Off-Boarding
  11. 11 Case Study: ASP.NET MVC Core
  12. 12 Tooling: Try it on your own Code
  13. 13 Analysing Microservice Architectures
  14. 14 Aggregation: Architectural Hotspots in Spinnaker
  15. 15 Microservice Dependencies: The Impact of Change
  16. 16 Change Coupling: Component or Feature Teams?
  17. 17 Dependencies and Teams: Locality of Change
  18. 18 Re-Think Software Architectures: From Accidental to Essential

Never Stop Learning.

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

Someone learning on their laptop while sitting on the floor.