# What does "love your reviwer" look like right now? — retained record

> Retained reddit record from reddit:ExperiencedDevs.

Canonical: https://highsignal.app/data/records/3e0066faded7d52e

[← sources](https://highsignal.app/data)


source: [reddit](https://highsignal.app/data/reddit) (reddit:ExperiencedDevs)  published 2026-10-26 15:18 ingested 2026-10-27 02:36

[original source ↗](https://www.reddit.com/r/ExperiencedDevs/comments/1xfzpny/what_does_love_your_reviwer_look_like_right_now/)

## retained text



```
I still believe in code review. It's the one place that - if you have a teammate that wants to push out slop - you can pump the brakes. And I'm very fortunate in that I work at a place that still cares about code quality.

But I have an issue with code reviews - they tend to be \*way\* more effort for the reviewer than the author of the PR. As someone who puts up PRs for review, I want to make the reviewer's life as easy as possible.

How do other teams achieve this? I tried Github stacked PRs - and they were great for review - but merging them in was a nightmare. The other habit I've been doing is a "self-review" where I submit a review of my own code in the PR to help guide the reviewer and signpost important parts. I also always offer to talk through the PR verbally.

Any other habits you all have that keeps code review easier for the reviewer?
```



document fetched 2026-10-27 00:26 · canonical https://reddit.com/r/ExperiencedDevs/comments/1xfzpny/what_does_love_your_reviwer_look_like_right_now
