~/talk

Cracking the Code Review

Talkat Voxxed Days Ticino 2025 · 2025-01-16..01-17· [developer-experience]
slides:none on file

Claims that poorly timed reviews cost huge sums — citing $316 billion in 2013 — drive concrete fixes: enforce linted PR titles and conventional commits, add PR templates with checklists, require self-review and targeted reviewer tags, and use automation like inline code coverage, OpenRewrite and Google Java Format to remove noise. Examples include automating style fixes, detecting dead code and missing assertions, offering apply suggestions for one-click changes, and enforcing architecture rules with ArchUnit — these interventions noticeably shrink churn and speed merges.

AI-written summary · about

  1. 0:00Code review importance
  2. 1:04Cost of bugs and benefits
  3. 2:06What is code review
  4. 3:12When code reviews may not be necessary
  5. 3:55Review-friendly pull requests
  6. 6:03Clear PR titles and descriptions
  7. 8:29Effective PR descriptions
  8. 9:55Examples and context in PRs
  9. 11:17PR templates and checklists
  10. 12:00Self-reviewing PRs
  11. 12:42Documenting changes in PRs
  12. 14:07Requesting reviews efficiently
  13. 15:52Context and urgency in requests
  14. 16:34Human factors in reviews
  15. 17:36Tone and social skills
  16. 17:57Vague feedback issues
  17. 18:41Endless PR discussions
  18. 19:22Responding to feedback
  19. 20:04Giving reviews as reviewer
  20. 20:25When to start reviewing
  21. 21:29PR review responsibility
  22. 22:12How to review a PR
  23. 22:33Reading PR descriptions first
  24. 23:36Prioritizing review feedback
  25. 24:18Functionality and tests focus
  26. 25:42Tools for efficient reviews
  27. 26:44Editor for better reviews
  28. 27:50Constructive review comments
  29. 28:53Words in review feedback
  30. 30:39Specificity and ambiguity
  31. 31:40Suggestions and alternatives
  32. 32:42Positives in code reviews
  33. 33:46Avoiding bike shedding
  34. 34:49Automating trivial discussions
  35. 36:12Static analysis tools
  36. 38:44Automating migrations
  37. 39:26Consistent code formatting
  38. 40:50Opinionated formatting tools
  39. 41:51ArchUnit architectural rules
  40. 43:14Implementing tools gradually
  41. 43:57Effective code review takeaways
  42. 44:18Closing remarks and Q&A
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 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
?
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.