Skip to content

Instantly share code, notes, and snippets.

@michaeldorner
Last active December 5, 2018 16:15
Show Gist options
  • Save michaeldorner/fad5f5c5510cde87a919a8867b19d313 to your computer and use it in GitHub Desktop.
Save michaeldorner/fad5f5c5510cde87a919a8867b19d313 to your computer and use it in GitHub Desktop.

Pervasion of and Motivation behind Code Review

Question 1: Do you review code as part of your daily work?

  • Rationale: We want to understand why developers review code. Our research indicated, that some just do not or if they do, they are forced to do so, but do not see any value in reviewing code.
  • Answers: Single choice with
    • No.
    • Yes, because I was told to do so.
    • Yes, because I see value in code review.

Question 2: How many hours per week do you spend with code review in average?

  • Rationale: We know that every Microsoft developer spends about 2 - 6 hours per week in average on code review, but there are no comparable numbers.
  • Answers: A number.

Question 3: How many different developers per week do you review code from?

  • Rationale: One huge benefit of code review is the knowledge sharing. Knowledge can be spread over a network only if there is a sufficient large network. However, we do not know an average-sized code review network.
  • Answers: A number.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment