~/talk

Skills for debugging complex problems

Talkat UtahJS Conf 2023 · on Friday, 2023-09-15· [developer-experience]
slides:none on file

Fixes start with concrete measurements and fast feedback: a serger timing fix requires a caliper and 18 millimeters and failed because two screws slipped on a square rod, not because timing was off, avoiding a $250 repair. Debugging environments split into on‑call chaos and deep work; use breathing, an incident manager, and breaks. Eliminate anchoring (the doubling trap), iterate with quick tests, use distributed tracing instead of hunting logs, and prepare a minimal complete verifiable example and a post‑mortem to improve the loop.

AI-written summary · about

  1. 0:00Debugging everyday problems
  2. 2:31Debugging in high-pressure
  3. 5:11Self-care during debugging
  4. 8:43Focus rituals for problems
  5. 13:01Eliminating cognitive bias
  6. 15:52Fast feedback cycles
  7. 18:20Asking effective questions
  8. 20:52Improving observability
  9. 21:34Post-mortem improvements
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 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
?
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.