As developers, we have a unique problem: our distraction machine IS our work machine. You cannot put your laptop in another room when your job requires staring at it for 8 hours.
I tracked my actual productive coding time for a month using WakaTime. The results were brutal: out of 8 "work hours," I was averaging 2.5 hours of real coding. The rest? YouTube rabbit holes. Reddit threads. Twitter arguments. HN comment sections.
I was not lazy. I was fighting a battle I could not win with willpower alone.
The Root Cause
Every time I hit a hard bug or a boring task, my brain would instinctively open a new tab. Not consciously — it was muscle memory. And within 0.5 seconds, an algorithmic feed was serving me perfectly-curated dopamine hits.
- YouTube Home: "Here are 47 videos you'll find irresistible"
- Reddit front page: "Here's a rage-inducing thread about your favorite framework"
- Twitter For You: "Here's some drama in the tech community"
The platforms are not neutral tools. They are attention extraction machines. And they are really good at their job.
The Fix (Not What I Expected)
I tried every blocker out there. Cold Turkey, Freedom, SelfControl, /etc/hosts hacks, browser extensions. They all failed for one of two reasons:
- They blocked too much. I need YouTube for tutorials. I need Reddit for r/webdev and Stack Overflow alternatives. I need Twitter for release announcements.
- I could turn them off. Every single one had an escape hatch I'd exploit at 2 PM on a Tuesday.
Then I found Monk Mode which takes a fundamentally different approach:
Selective Feed Blocking
Instead of blocking YouTube entirely, it blocks:
- ❌ YouTube Home page
- ❌ YouTube Shorts
- ❌ Recommendation sidebar
- ❌ Autoplay
- ✅ YouTube Search (works perfectly)
- ✅ Direct video links (works perfectly)
Same for Reddit (home feed gone, subreddits work) and Twitter (For You gone, search works).
This means when my ADHD brain opens YouTube during a hard bug, there's nothing there. Just a search bar. No dopamine hit. Brain goes "boring" and returns to the code.
Locked Focus Sessions
The killer feature: start a focus timer (I do 90-minute blocks) and everything locks down. No override. Not a password, not a setting, nothing. The timer runs and you code.
This sounds extreme until you realize it's the same thing as working at a coffee shop without wifi. You're not more disciplined there — the environment just doesn't offer the easy exit.
The Results
Week 1-2 with Monk Mode:
- WakaTime coding hours: 2.5h/day → 5.8h/day
- Shipped: auth system + API redesign + 3 bug fixes
- Context switches: ~40/day → ~8/day
For context, the auth system alone had been
"in progress" for 6 weeks before this.
The math is simple: if you go from 2.5 to 5.8 hours of actual coding, you're 2.3x more productive without working longer hours. You just removed the dead time.
My Setup
- Monk Mode for selective feed blocking + locked sessions
- WakaTime for tracking actual coding time (accountability)
- 90/15 blocks: 90 min locked coding, 15 min free browsing
- "Feed-free" as default: algorithmic feeds are always blocked, even outside focus sessions
The Meta-Lesson
We spend so much time optimizing our dev tools — terminal configs, editor plugins, CI pipelines — but the single biggest performance bottleneck for most developers is attention fragmentation.
You don't need a faster build system. You need to stop opening YouTube when webpack is compiling.
Monk Mode for Mac — $15 one-time, no subscription. Native macOS, Apple Silicon. Use code DEV for $5 off.
Curious what other devs use for focus. Drop your setup in the comments.
Top comments (0)