Code Review

12345678910111213141516171819202122232425262728
Across
  1. 2. what a primary reviewer should be with the area of code
  2. 4. no more than needed
  3. 9. great engineers listen to them
  4. 10. the desired size of a PR
  5. 11. needed on every PR
  6. 12. must be considered and tested
  7. 13. opportunity for standardization or reuse
  8. 15. improves quality and facilitates learning
  9. 18. should be descriptive
  10. 19. check IntelliJ and eliminate them
  11. 20. is it a good one?
  12. 25. should have CRAB and summary
  13. 26. should summarize the change
  14. 27. keeps focus off the trivial
Down
  1. 1. review before adding reviewers
  2. 3. needed for backports
  3. 4. explain why not what
  4. 5. these should be removed
  5. 6. working together to improve code quality
  6. 7. considered to get from here to there
  7. 8. no longer needed
  8. 14. needed on every pull request
  9. 16. the PR relation to the whole system
  10. 17. codifies best practices
  11. 21. unscripted testing
  12. 22. a minor comment for education or polish
  13. 23. enshure it's correct
  14. 24. should sufficiently cover
  15. 28. consider customers when user facing