Code Review Etiquette For The Modern Developer

No, it’s not just LGTM. It’s about far more than just LGTMs and GEFNs. Sure, the little rocket  and  emojis help, but that isn’t what code review is all about, and it never was. If code reviews for you are a checkbox exercise, you’re in the right place. If code reviews for you are what slows you down, you’re also in the right place. Frankly, regardless of what your relationship with code reviews is, you’re probably still going to learn something today, so keep reading. <h2>High priority</h2> Opinions on this may vary, but the way I look at it is from a team perspective. A pull-request (PR), is an attempt to get some work done, move it to the next stage. That isn’t an individual goal, that is a team goal. If every team member only cares about themselves and the work they do, you don’t have a team, and you’re unlikely to succeed. This is why, for the last few years, I have made it my priority to review people’s code as soon as they submit a PR. Learning to break your own flow to help the team succeed will make you a better engineer and help <a href="https://levelup.gitconnected.com/context-switching-can-improve-developer-performance-and-boost-your-career-101f3a3f5ad1" rel="noopener ugc nofollow" target="_blank">you learn that context switching can actually work in your favour</a>. If everyone starts doing this on the team, you suddenly find your PRs reviewed and maybe even approved within just a few minutes. <a href="https://attilavago.medium.com/code-review-etiquette-for-the-modern-developer-3fb5e1ad62d0">Click Here</a>