What if designers approached collaboration and critique more like developers? Could it make us better designers, and could it better collaboration between designers and developers? Presented at Yggdrasil 2018 in Sandefjord, Norway
11. “Code review is systematic examination […] of
computer source code. It is intended to find mistakes
overlooked in software development, improving the
overall quality of software. Reviews are done in various
forms such as pair programming, informal
walkthroughs, and formal inspections.
Wikipedia
13. Pull request submitted by ingvilin
#423 Add onboarding status
To keep track of the
onoardingProgress a default
onboarding progress object is
added to the users metadata on
completing the sign up process.
ingvilin requested a review from
daginge
22. “Code reviews set the tone for the entire company that
everything we do should be open to scrutiny from
others, and that such scrutiny should be a welcome
part of your workflow rather than viewed as
threatening.
Bruce Johnson, co-founder of Full Story
23. “Code reviews set the tone for the entire company that
everything we do should be open to scrutiny from
others, and that such scrutiny should be a welcome
part of your workflow rather than viewed as
threatening.
Me
64. Review walkthroughs
• Walkthrough is done together
• One person in charge of reviewing and documenting
• Choose a format that gives as much context as possible
• The idea is to identify issues, not necessarily solve them
