Code review feedback has a weird side effect: it can send you straight into a scroll.
Not because the review was bad. Not because you are lazy. Because there is a tiny emotional spike between reading the comment and deciding what to do next.
You see:
- a nit you disagree with
- a bigger refactor than you expected
- a question you should have answered in the PR description
- a failing assumption
- a comment that is technically right but still annoying
That is the moment your hand reaches for the phone.
The code-review feedback rule
When you open review feedback, block your highest-risk social apps for 15 minutes.
Then do only this:
- read every comment once
- write the smallest next action beside each one
- fix the easiest comment first
- leave the emotional comment for last
- do not open a feed until one comment is resolved
The goal is not to become a perfect focus robot. The goal is to protect the first few minutes after feedback, because that is when a tiny frustration turns into TikTok, Reels, YouTube Shorts, Reddit, or another loop.
Why Screen Time usually fails here
Apple Screen Time can report that you spent 38 minutes in social media.
That is useful after the damage.
But review feedback is not a reporting problem. It is an enforcement problem.
A better Screen Time alternative for this moment is an iPhone app blocker rule that starts before the app opens:
- block the social app
- block the website fallback too
- use an open limit if you still need the app later
- use strict mode when you know you will negotiate
- check blocked-attempt logs after the session
The important part is making the easy escape unavailable while the frustration is fresh.
A practical setup
Pick one review trigger:
- opening GitHub review comments
- seeing a requested changes notification
- getting CI plus reviewer feedback at the same time
- rereading a comment you are annoyed by
Then set a short focus session around it.
For example:
For 15 minutes after opening review feedback, block TikTok, Instagram, YouTube Shorts, Reddit, and the same sites in Safari.
If you use an app blocker for iPhone, keep the rule small. One review session. One time window. One boundary.
That is easier to keep than pretending you will never scroll again.
Why I am building Monk Mode around this
Monk Mode is my attempt to make these tiny failure moments enforceable.
It is an iPhone app blocker and social media blocker for people who need something stricter than Screen Time. It supports app and website blocking, open limits, strict modes, focus sessions, recovery analytics, and blocked-attempt logs.
The positioning is simple: distraction is not a motivation problem. It is an enforcement problem.
If you want to try it, here is Monk Mode:
https://www.monk-mode.lifestyle/index.html#pricing
The small rule
Do not wait until you have already lost half an hour.
If code review feedback tends to send you into a loop, block the loop before reading the comments.
Fifteen minutes is enough to turn review feedback from an emotional interruption back into a list of fixes.
Top comments (0)