Code Review Steps to Consider

Prepare a code review, but don't make it generally available yet. Give your brain a break then review the code yourself.
1. As your reviewing the code make notes of the following:
  1. Does what you have written meet the definition of done?
  2. Did you add a bug?
  3. Did you get tired and code something poorly?
2. Keep a tally of these items so you can personally track your own errors.
3. Use this to inform future code reviews and continually improve your abilities.
Did you follow best practices?
1. Did you follow industry best practices?
2. Did you follow language best practices?
3. Did you follow your team's best practices?
Can other people read your code?
1. Assume they can't and think about where people might struggle the most.
2. Are there magic numbers/words?
3. Is your code commented appropriately?
  1. Are there no comments or too few comments?
  2. Are there too many comments suggesting that your code is hard to understand?
Are there tests?
1. Do the tests cover the expected changes in behavior?
2. Do the tests make sense? E.g., are your unit tests real unit tests or are they integration tests?
3. Have you considered edge case?
4. Do you test bad as well as good inputs?
5. Have you considered null cases?
Go over your naming conventions and see if they make sense.
1. Do methods, variables, and classes follow naming conventions, i.e., verb_a_noun vs. noun_verber
2. Do names correctly indicate what the thing does, could they be misconstrued?
3. Could the names be shortened or lengthened to be made more clear?
Did you run a linter, etc.?
After getting comments, have you validated that your changes work?

Brainstorm - Reviewing Code Reviews

Everything committed?
Commit is in correct format?
Is Jira or other tracking software updated?
Is the code structure correct?
Did you consider other alternatives when coding, especially in libs, patterns, etc.?
Did you follow OO practices? Could something be factored out, reused, etc.?
Is all documentation updated, READMEs, Javadocs, comments, etc.?
Do you have the correct level of mutability?
Have you considered error handling?
Do your tests test something? Or do they just exercise code? Can your tests fail?
Are their vestigial portions of code that can be removed?
Can something be factored out?

	Erstellt von Alex Poiry vor mehr als 6 Jahre

General ideas around good code review practices