How this course will work:

My goal in this course is not to slam you with 70 hours of video: it is, instead, to give you the tools to get rolling as precisely and expediently as I can, because I know your time is valuable.

    1. Introduction

    2. How This Course Works

    3. Misconceptions about Technical Debt

    4. Critical Concept: Maintenance Load

    5. Critical Concept: Context Loss

    6. So what is tech debt, then?

    7. How fast does maintenance load rise?

    8. Practice Analyzing Maintenance Loads

    9. Critical Concept: Code Stewardship

    10. Code Stewardship Skill: Writing Discoverable Code

    11. Code Stewardship Skill: Writing Flexible Code

    12. Code Stewardship Skill: Documenting Code

    13. Code Stewardship Skill: Context Transfer

    14. An Expansive View of Code Stewardship

    15. Systemic Causes of High Maintenance Load Accrual

    16. How would you incentivize code stewardship?

    1. Why "Tech Debt Week" Doesn't Work

    2. Reflection: Code Renovations

    3. Gathering Clues About Your Maintenance Load

    4. Reflection: Existing Maintenance Load Priorities

    5. Prioritizing High Leverage Code Changes

    6. Priority Group 1: Feature Bloat

    7. Priority Group 2: Documented Holdups

    8. Priority Group 3: Addressing Abandoned Houses

    9. Priority Group 4: Strategic Code Flexibility

    10. Priority Group 5: Equipping Engineers to Suggest Streamlining Options

    1. Introducing: A Simulation Exercise!

    2. Ticket 1: Email Restaurant Recommendation to a Friend

    3. Ticket 2: Social Auth is Handle Dependent

    4. Ticket 3: Time Zone Adjustment

    5. Ticket 4: Functional Navigation

    6. Ticket 5: Object Oriented Restaurant Code

    7. Ticket 6: Case Sensitive API Endpoints

    8. What were YOUR Answers?

    9. Wrapping Up

Learn a system for addressing technical debt

  • $219.00
  • 35 lessons
  • 2.5 hours of video content
  • We'll begin with a specific definition of technical debt. Then we'll address how maintenance load accumulates and discuss how to slow the growth of maintenance load. We'll then move on to addressing existing maintenance load to get a team out from underwater fast.

Learn a system for addressing technical debt.