Overview
Dive into a comprehensive workshop on tackling technical debt through an analytical approach. Learn to measure and prioritize areas of highest need, identify high-leverage code changes, and distinguish them from mere renovations. Explore strategies for preventing and reducing technical debt, including code stewardship, addressing malleability rigidity, and implementing data-driven targets. Gain practical insights on identifying culprits, removing feature bloat, addressing documented UPS and abandoned houses, and making upfront investments. Discover how to transform the seemingly Sisyphean task of managing technical debt into a structured, manageable process that can prevent code bankruptcy and system rewrites.
Syllabus
Intro
Workshop Overview
What is Technical Debt
Maintenance Load
Context Loss
Technical Debt
Signs of Technical Debt
Individual Question
Cliffhanger
Code Stewardship
Malleability Rigidity
Individual Exercise
Examples
Break
Technical Debt First Steps
Step 1 Identify Culprits
Code Renovations
Code Renovation
Data Driven Targets
High Leverage Changes
Remove Feature Bloat
Address documented ups
Address abandoned houses
Upfront investment
Taught by
Ruby Central