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