~/talk

Documentation - Because Everyone Dies!

links:none on file
slides:none on file

A real-case pitch for tiny, practical documentation: a commented CSS file teaches a new dev in two weeks; a missing-docs outage costs the site tens of pounds and stalls recovery until someone with knowledge returns. Use inline comments, 5-second comments, internal Confluence pages, short how-to ordered lists or a reseller data-protection guide. Document what connects to what, update notes when the fix changes, and treat docs as living artifacts—small notes save hours, prove work, and let others restore or extend sites without hand-holding.

AI-written summary · about

  1. 0:00Why document your work
  2. 3:40Personal benefits of documentation
  3. 5:53Helping coworkers with documentation
  4. 7:39Documentation is easier than you think
  5. 11:23What counts as documentation
  6. 13:09Tips for writing good documentation
  7. 15:19Keeping documentation up to date
  8. 16:30Examples of great documentation
  9. 17:16Closing and Q&A
~/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.