--

Useful article, thanks. I mostly just read through the code comments as soon as the PR is turned in to see if "the next dev hired" would be able to maintain it. If so, I approve, merge, and send it to QA.

One tip I didn't see is that it's faster to have the reviewer merge than sending it back to the author when a PR is approved. That can save a lot of time especially on async distributed teams.

--

--

Dr. Derek Austin 🥳
Dr. Derek Austin 🥳

Written by Dr. Derek Austin 🥳

Hi, I'm Doctor Derek! I've been a professional web developer since 2005, and I love writing about programming with JavaScript, TypeScript, React, Next.js & Git.

Responses (2)