~/talk

Playing Well With Others – Writing Solid Code in Large Community Projects

Talkat WordCamp US 2015 · 2015-12-04..12-06· [developer-experience]
links:none on file
slides:none on file

Large community projects succeed when code assumes other people will read and reuse it: treat input conservatively, validate type and range, and make failures explicit — prefer return a single type instead of sometimes-null or mixed values. Calls out WordPress examples like get_post and wp_insert_post; recommends using PHP list() to return (post_id, has_error boolean), run static analysis, keep comments that explain non‑obvious choices and data shapes, and blow up early so bugs surface quickly.

AI-written summary · about

  1. 0:00Start
  2. 0:41THE SECRET
  3. 2:53EDGE CASES
  4. 4:29BOUNDARY CONDITIONS
  5. 5:21INPUT IS AGGRESSIVE
  6. 8:00LIBERAL INPUT
  7. 9:19CONSERVATIVE INPUT
  8. 10:44ESCHEW OBFUSCATION
  9. 11:37RETURN A LEGITIMATE VALUE
  10. 12:44RETURN A SINGLE TYPE
  11. 13:41FAILURE MODES?
  12. 15:20FILL IN THE GAPS
  13. 16:50DESCRIBE HOW IT COULD HAVE BEEN
  14. 18:29DESCRIBE ABNORMALITIES
  15. 19:13POINT OUT RISKS
  16. 20:32TRIVIALIZE TRIVIA
  17. 25:49WHEN YOU JUST GOTTA
  18. 26:02A SNEAKY ALGORITHM
  19. 26:31DUAL ALGORITHMS FOR DEV WORK
  20. 26:46DUAL ALGORITHMS FOR LIVE TESTS
~/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.