Refactoring CSS Without Losing Your Mind
summary
Argues that refactoring must be specific: prove costs with numbers (theme hacks total 9 days versus a 7‑day refactor), avoid giant “refactoring tunnels,” and prefer many small scoped refactors (nav, buttons). Recommends techniques that actually work: use all:initial to stop style leakage, run a temporary defense.css (used at Sky) to reconcile old and new toolkits, mark completed code with RF- classes, stash hacks in shame.css, and apply specificity hacks (IDs as attribute selectors, :root) instead of spraying !important.
AI-written summary · about
chapters (15)
- 0:00Intro
- 1:23HI, I'M HARRY
- 3:41THREE KINDS OF REFACTORING
- 7:13TECHNICAL DEBT
- 8:04WHEN TO REFACTOR
- 11:10WHEN NOT TO REFACTOR
- 13:25UGLY CODE
- 16:18REFACTORING TUNNELS
- 18:06REFACTOR IN ISOLATION
- 22:16SKY UI TOOLKIT
- 27:31HACKING SPECIFICITY
- 30:17THESE ARE HACKS
- 31:47ISOLATE HACKS
- 33:01SHAME.CSS
- 40:26REMEMBER
