~/talk

The art of the code review

Talkat WordCamp Europe 2023 · 2023-06-08..06-10· [developer-experience, testing]
name:Tim Nash
links:none on file
slides:none on file

Code reviews cut defects and single points of failure by combining automate tests and linters (GitHub Actions, unit/acceptance tests, pre-commit hooks) with human checks; the talk gives a real case where refund code silently charged someone for 40 years and lived in the codebase for 4–5 years until reviews and tests caught issues. Recommendations: keep changes small, run CI before asking for review, involve specialists (security, accessibility), give timely actionable comments, and use pair programming or PR-based workflows to get working code into production faster.

AI-written summary · about

  1. 0:00Introduction to code reviews
  2. 4:20Why code reviews matter
  3. 10:44Knowledge sharing in reviews
  4. 15:12Who should review code
  5. 20:11Where to conduct reviews
  6. 22:20Art of giving feedback
  7. 29:04Language and tone in reviews
  8. 31:53Q&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.