Peer Code Review

Session Overview

  • Considerations
  • Peer Code Review

Peer Code Review

Why Peer Code Review?

Peer Code Review

What should we look for in Peer Code Review?

Peer Code Review

How should we communicate during Peer Code Review?

Peer Code Review

Peer Code Review

  1. You will be paired with an individual from another team.
  2. Briefly introduce the codebase and make sure they have access to the repo
  3. Spend ~15-20min reviewing the code base.
  4. Jointly work through the code review.
  5. Fill out previous feedback grid and communicate with partner.

Next Steps

To think about:

  • README
  • Model storage
  • Notebooks versus scripts?
  • Starting point? Where to begin?
  • Where is the flow? What is the flow?
  • Blocks of commented out code
  • Context for jupyter notebooks - Header? Explanation? Executive summary?
  • Clean out checkpoints, pycache -> Use gitignore! :)
  • File Extensions! :)
  • Remove Data from Gitlab repo
  • Other Items?