~/talk

How to Accidentally Destroy a Codebase (A Step-by-Step Guide)

Talkat NDC Oslo 2026 · 2026-09-14..09-18· [angular, frontend-architecture]
links:none on file
slides:none on file

A small Angular to‑do app starts at ~120 lines and four files and gets wrecked step‑by‑step: a quick fix with magic "urgent" string hides priority, a premature abstraction via a generic CRUD base adds debt, a useless cache without invalidation and manual change‑detection slow things, a growing set of booleans creates impossible states, and onion layering multiplies files until the repo is ~300 lines across 14 files. Each change compiles and looks clean; practical alternatives: add a priority type, follow the rule of three, measure before optimizing, use discriminated unions, and avoid needless layers.

AI-written summary · about

  1. 0:00Introduction and setup
  2. 3:27Baseline application
  3. 5:29The quick fix
  4. 9:20Premature abstraction
  5. 12:25Caching without invalidation
  6. 16:15Manual change detection
  7. 20:15Boolean flag explosion
  8. 25:41Best-practice cosplay
  9. 27:40Autopsy of the codebase
  10. 28:48Lessons and rewind
~/search
type to search 6,518 conferences, 143,918 speakers and 192,133 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
← →
on a talk: 5 seconds back / forward
0–9
on a talk: jump to 0%–90% of the recording
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.