Главная
Study mode:
on
1
Intro
2
Workshop Overview
3
What is Technical Debt
4
Maintenance Load
5
Context Loss
6
Technical Debt
7
Signs of Technical Debt
8
Individual Question
9
Cliffhanger
10
Code Stewardship
11
Malleability Rigidity
12
Individual Exercise
13
Examples
14
Break
15
Technical Debt First Steps
16
Step 1 Identify Culprits
17
Code Renovations
18
Code Renovation
19
Data Driven Targets
20
High Leverage Changes
21
Remove Feature Bloat
22
Address documented ups
23
Address abandoned houses
24
Upfront investment
Description:
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.

Workshop - Tackling Technical Debt - An Analytical Approach

Ruby Central
Add to list
0:00 / 0:00