~/talk

Effective code reviews

Talkat JDD 2017 · 2017-10-03..10-04· [developer-experience]
links:none on file
slides:none on file

Covers why code review matters for software quality and the benefits it brings, aimed both at developers who skip reviews and those who perform them reluctantly. Provides concrete hints and tips for conducting code reviews more effectively, but does not focus on any specific tools or languages.

AI-written summary · about

  1. 0:00Effective Code Reviews
  2. 3:45Why is it worth my time?
  3. 4:52public boolean isDisabled() return enabled
  4. 7:18New guy in the team
  5. 10:20New AWESOME idea to be implemented
  6. 14:09OK. I made a change. How to raise a review?
  7. 15:131 ISSUE = 1 CODE REVIEW
  8. 16:32180 changed files Hours spent on reviewing
  9. 21:22Put context on the review
  10. 23:33Add comments and resources
  11. 25:11Mark important/risky changes
  12. 27:14Opposite side of the same fence
  13. 29:16Understand the reasons of the changes
  14. 33:13Beware of the scope creep
  15. 33:52Adopt positive attitude
  16. 34:30TDD Kata
  17. 35:02Code review Kata
  18. 36:31Thank you
~/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.