~/talk

Documentation for developers: A gift to your future self

slides:none on file

Emphasizes concrete practices: build a component spreadsheet with screenshots and names and export to Storybook or a Google Sheets template; write short, action‑titled tasks (create, add, change) so work is chunking‑friendly and jumpable; leave code comments with URLs and create ADR (architecture decision record) files for long‑term choices; use meeting templates, Fireflies/Otter transcripts, Notion or Asana integrations, and a simple “checking out” note before switching contexts; cites a 12,000‑word feature doc and hiring 18 front‑end developers as practical outcomes.

AI-written summary · about

  1. 0:00Introduction to talk
  2. 4:35Preparing and planning stage
  3. 13:57Managing the messy middle
  4. 21:40Documenting code and decisions
  5. 27:20Post-project documentation value
  6. 33:58Building collective knowledge
  7. 37:28Effectiveness over efficiency
  8. 38:30Q&A session
~/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.