Every developer I've spoken to on a team >1 has complained about PR review burnout, no understanding of the codebase anymore and even a lost love for the craft. I think this is primarily happening because every PR reads like its written by a distinguished engineer. (Why say lot word when few word do trick??!!)
Everyone reviews PRs differently but I've personally started relying more on visualisations to get an initial sense of what's happening. So this is my attempt at a skill and a UI kit to help me understand PRs faster. Bugbots help but not really because the purpose of reviews is to build shared understanding! Shoutout to Blake Smith (https://blakesmith.me/2015/02/09/code-review-essentials-for-...).
Every developer I've spoken to on a team >1 has complained about PR review burnout, no understanding of the codebase anymore and even a lost love for the craft. I think this is primarily happening because every PR reads like its written by a distinguished engineer. (Why say lot word when few word do trick??!!)
Everyone reviews PRs differently but I've personally started relying more on visualisations to get an initial sense of what's happening. So this is my attempt at a skill and a UI kit to help me understand PRs faster. Bugbots help but not really because the purpose of reviews is to build shared understanding! Shoutout to Blake Smith (https://blakesmith.me/2015/02/09/code-review-essentials-for-...).
I'd love to get HN's take on this :)