~/talk

Code Review as a Collaborative Journey

Talkat DroidKaigi 2019 · 2019-02-07..02-08· [developer-experience, soft-skills]
links:none on file
links:none on file
slides:none on file

Defines code review as a collaborative journey with explicit steps: state the goal and background, describe strategy, include verification steps, run and compile the app (use a separate checkout with git worktree to avoid build failures), inspect UI, lifecycle and performance, run the memory profiler for leaks, review layout XML and added libraries, and prioritize feedback into actionable items; recommends templates in pull requests and giving clear, testable suggestions rather than nitpicks.

AI-written summary · about

  1. 0:00Code Review as a Collaborative Journey
  2. 2:01What is Code Review For?
  3. 9:07The Story of Code Review
  4. 9:42Understand the Background and the Goal
  5. 11:31Verify if the Change Really Takes You to the Goal
  6. 12:52Look into Every Changes One by One
  7. 13:50Look Back on the Change from the Goal
  8. 14:55Have a Conversation with the Reviewee
~/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.