Code reviews.   You know how important they are.  They are one of the pillars of getting... Tagged with codereview, productivity, learning, testing.

Materialize

Bobby Iliev

DevOps

Community Picks is a section on daily.dev where our community members share the most interesting and valuable content they've discovered online. From insightful articles to handy tools, every post is a gem curated by our dedicated coomunity. To contribute to Community Picks, you need to have at least 250 reputation points, ensuring that only active and trusted members can share their finds.

Community Picks

This post discusses the importance of code reviews, the impact of long review cycles on lead time, and strategies for making code reviews more effective and efficient. It also introduces the DORA metrics and highlights the role of constructive feedback and a positive feedback culture in improving code quality and team morale.

The Senior Engineer's Guide to Code Reviews

My team already does reviews. Why should I care?

Great! How? 👉 Strategies for Faster, More Effective Reviews

<p>Some good info, but article just feels like a promotion for their product.</p>


<p>Hi there! I’d be happy to share some insights on our code review process. I highly recommend EsLint or SonaLint if you want to have some code style checks before you make your commit. It’s also super important that all developers take care of the lines flagged by these extensions. In our case, we had a big gap in our knowledge regarding our warehouse management system. So, what could we do to fix this?  We got together a group of experts and jotted down a few ideas. After much discussion, we decided the best solution was to form coding pairs. What do you mean ?!, coding pairs? Absolutely! And you’ll see why in a moment. We thought it would be a great idea if each expert had at least one coding partner. It’s not that they write code together, but that the expert reviews the partner’s code and vice versa. There will also be a meeting where both can talk about their code decisions or misunderstandings. The things mentioned in the first few lines in the article are the basis for this ( style checks, tests… ). It’s worked pretty well for us because we’ve closed the knowledge gaps and reduced code review time because now everyone can do good code reviews. I really hope this has helped in some way.</p>
