3
2 Comments

I shipped more in one month than the previous quarter by just blocking distractions

Last quarter I shipped 2 features. This month I shipped 6.

The only thing I changed: I started using Monk Mode for Mac to block distractions during work hours.

I'm an indie hacker building solo. Nobody's watching over me. No standup meetings. No accountability partner. Just me, my Mac, and an infinite supply of distractions.

My old pattern:

  • Open VS Code with good intentions
  • Hit a difficult problem after 20 minutes
  • "Let me just check X real quick" (translation: 40 minutes gone)
  • Come back, lost all context
  • Spend 15 min getting back into the code
  • Repeat 5-6 times per day

I was "working" 8 hours but producing maybe 3 hours of actual output.

Here's what Monk Mode changed:

  1. Recurring focus blocks run automatically (8:30-12, 1-5, M-F). I don't decide to start them. They just happen.

  2. During blocks, X/YouTube/Reddit/HN are blocked. Not hidden. BLOCKED. With strict mode + PIN + Touch ID, I physically cannot access them on impulse.

  3. Feed cleanup strips the addictive parts of sites I still need. YouTube works for tutorials but Shorts is gone. X works for DMs but For You is gone.

  4. Daily caps let me have 15 min/day of "leisure browsing." Forces me to be intentional about it.

  5. Analytics show me my focus score, streaks, and — most importantly — bypass attempts. Watching that number drop from 30+/day to under 5 was incredibly motivating.

The result: longer unbroken focus blocks, more features shipped, less guilt about wasted days.

If you're building solo on Mac and losing hours to distractions:
https://mac.monk-mode.lifestyle

$15 lifetime. Code DEV = $5 off.

on March 5, 2026
  1. 1

    The no-standup thing hits. When you're solo there's no external pressure to close tasks, so the drag of distractions compounds more than it would on a team. The counter-pressure has to be internal or automated, and sounds like you found that.

  2. 1

    I’ve noticed a similar pattern while building solo.

    The biggest productivity killer for me wasn’t the time spent on distractions — it was the context reset afterward. Even a 2–3 minute interruption can cost 10–15 minutes to fully reconstruct the mental model of what the code was doing.

    So blocking distractions helps not only because you “waste less time”, but because you protect the continuity of thinking.

    Out of curiosity — did your average PR size or cycle time change once you started working in longer uninterrupted blocks?

Trending on Indie Hackers
Your AI Product Is Not A Real Business User Avatar 116 comments Stop Building Features: Why 80% of Your Roadmap is a Waste of Time User Avatar 79 comments I built an enterprise AI chatbot platform solo — 6 microservices, 7 channels, and Claude Code as my co-developer User Avatar 40 comments The Clarity Trap: Why “Pretty” Pages Kill Profits (And What To Do Instead) User Avatar 34 comments I got let go, spent 18 months building a productivity app, and now I'm taking it to Kickstarter User Avatar 23 comments I went from 40 support tickets/month to 8 — by stopping the question before it was asked User Avatar 19 comments