A flaky test creates a weird kind of waiting room.
You rerun it. It passes locally. CI fails. You change nothing. It passes again. Then you reach for your phone because your brain wants a quick hit of certainty while the machine decides whether your afternoon is ruined.
That is a perfect doomscrolling trigger because it feels justified. You are not "being lazy." You are waiting on feedback.
The problem is that your phone turns a 90-second wait into a 25-minute context leak.
Here is the rule I would use for that specific moment.
The flaky-test rule
Before rerunning a flaky test or waiting on CI, set a short phone boundary first.
- Start a 15-minute focus session.
- Block TikTok, Instagram, YouTube Shorts, Reels, and the backup websites you use when apps are blocked.
- Give messaging or work apps a low open limit if you genuinely need them.
- Turn on a stricter mode if you know you will override the limit while frustrated.
- After the test result lands, check the blocked-attempt log.
The goal is not to become a productivity robot. The goal is to remove the easiest escape hatch during a predictable waiting loop.
Why Screen Time often fails here
Apple Screen Time is useful as a baseline, but flaky-test waiting is too small and too emotional for soft limits.
The dangerous moment is not "I used YouTube for 2 hours today."
It is:
- I have 2 minutes until CI finishes.
- I am annoyed.
- I open one video.
- The test result arrives.
- I do not go back.
That is why this kind of rule works better as an iPhone app blocker setup than as a broad daily limit. You are protecting the trigger, not the whole day.
What to review later
If the blocked-attempt log shows a bunch of taps during test runs, that is useful data.
It means the boundary is catching a real reflex, not an imaginary discipline problem.
If there are no blocked attempts, loosen the rule. If there are ten, make the next debugging block stricter.
This is the part most focus systems miss. The useful question is not "am I motivated enough?" It is "which exact moment keeps breaking my attention?"
For flaky tests, that moment is usually the rerun wait.
Monk Mode is built around that kind of enforcement: app and website blocking, open limits, strict modes, focus sessions, recovery analytics, and blocked-attempt logs.
If you want a Screen Time alternative for these tiny doomscrolling loops, the Monk Mode iPhone app blocker is here:
Top comments (0)