A chunk of every developer's work is a code review, but are you doing it well?

AppUnite's platform is  dedicated to providing insights and resources for mobile app developers and product teams, focusing on mobile app development, UX design, and product strategy. Through articles, case studies, and workshops, AppUnite offers insights into building successful mobile applications. Developers and product managers can learn about mobile app architecture, UI/UX design principles, and agile development methodologies to create innovative and user-friendly apps.

AppUnite

A code review should almost always be your priority, says Maciej Kaszubowski. Be quick nobody wants to wait long for feedback while losing the momentum takes energy to get back to the given PR. If you're using Pomodoro or taking regular breaks, check if there are any PRs then and don't.

Code Review Best Practices

Things you should do before submitting a PR

Reviewing is getting easier by time for experienced devs. Easiest way is apply methods, patterns, structures for your code first, so it will be more comfortable to review. So useful article, thanks for good tricks 👍

we also practice along with making all those mr related steps automated through mr template and CI/CD.
so before MR gets created all checklist need to be passed.

Great article, we follow all of these guidelines at our place which is a blessing compared to my previous job. A well prepared PR/MR is half the work. :)

I have always found that you cant rely on all devs for this. I found that finding the right dev who looks for perfection and takes pride is a good person to have as a filter or QA.