~/talk

10 Tips for Clean Code

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

Argues that a little upfront discipline speeds delivery by avoiding the “big ball of mud” and cites studies showing developers spend over 10:1 reading versus writing; recommends concrete habits: meaningful names for variables and methods, the Boy Scout Rule (leave surrounding code cleaner), and the single responsibility principle to reduce argument bloat. Emphasizes unit and integration tests and test-driven development, shows WordPress and Ruby on Rails examples, and describes plugins written with minimal WP coupling so they can be extracted and reused.

AI-written summary · about

  1. 0:00Introduction to Clean Code
  2. 0:28The Cost of Messy Code
  3. 1:29Reading Code Takes Time
  4. 2:37Professional Responsibility
  5. 3:38Meaningful Names
  6. 4:31Intentional Functions
  7. 5:12The Problem with Comments
  8. 6:24The Boy Scout Rule
  9. 7:14Single Responsibility
  10. 8:45Writing Effective Tests
  11. 9:44Independent Architecture
  12. 10:48Continuous Practice
~/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.