Why you should review code & how to get started
Why review code?
I perform code reviews because:
- It gives me practice reading code.
- I learn more about the code base.
- I learn different styles and approaches to writing code.
- I understand what people are working on and what is changing.
- It helps my teammates improve their code, catch bugs, and get their code through the door.
- It earns respect from teammates.
Hopefully, you’re convinced you should make code review a habit. However, the biggest hurdle probably isn’t motivation, but uncertainty on how to get started.
Tips for reviewing code
Reviewing code when you’re starting at a company can feel daunting. Not only because of “imposter syndrome”, but also because you might not know enough about the code you’re reviewing to recognize anything that could or should be changed. …
Transitioning the code review tool of a monorepo
This is part of a blog series on managing monorepos. If you haven’t already, check out https://medium.com/compass-true-north/repositories-one-or-many-f9da590611af. More to come in the next few weeks!
At Compass, we have over 350 software engineers collaborating on a single monolithic repository (see our post on multi-repo vs monorepo) that is home to hundreds of our backend services.
We were using Gerrit as a code review tool for this monorepo but decided to switch over to Github. This is the story of that transition.
Why did we do this?
The benefits of Github that fueled the transition include:
- Many engineers have a preference for the Github UI over Gerrit’s…
About
