I realized recently that I am never bored. Not for a single minute. Something is always playing, loading, refreshing. When I wait for code to compile, I check my phone. When I wait for coffee to brew, I open a browser tab. When I sit on the toilet, I scroll through whatever feed is closest to my thumb.

I have not been alone with my own thoughts in months. Maybe longer.

This bothered me enough to try something: for one full workday, no screens during breaks. No phone, no podcast, no background video, no Twitter while a test runs. Work is work. Breaks are nothing.

Just me and the wall.

The First Hour Is Awful

I want to be honest about this. The discomfort starts immediately.

I pushed a build, waited for it to compile, and reached for my phone. It wasn't there (I'd put it in a drawer). So I sat there. Thirty seconds of nothing. My brain was screaming for input. Not because I needed information. Because silence felt wrong. Stillness felt like wasted time. The urge wasn't rational. It was physical, like an itch behind my eyes.

I understand, intellectually, that this is a conditioned response. Years of filling every gap with stimulus have trained my brain to expect constant input. Understanding that doesn't make the first hour less miserable. You just sit there, aware of every second, feeling like you should be doing something.

I didn't stare at a wall. I stared out the window. I noticed the tree outside my apartment has new leaves. I have lived here for two years and never noticed when the leaves come in.

Then Something Shifts

Around the second or third break, the discomfort faded. Not completely. But enough that I stopped counting the seconds. I sat with my coffee and just... sat. No agenda. No input. And my brain, deprived of external content, started generating its own.

I thought about a bug I'd been stuck on all morning. Not intentionally. The solution just appeared, fully formed, while I was looking at nothing. I went back to my desk and fixed it in four minutes. I had spent ninety minutes on that bug before the break. Four minutes after doing nothing.

This is the thing nobody tells you about boredom: your brain doesn't stop working when you stop feeding it. It switches modes. It goes from consuming to processing. All those inputs you've been shoveling in all day, the tweets, the articles, the Slack messages, the podcast in the background, they're occupying processing power that your brain could be using to actually think.

Mental bandwidth is finite. Every article you half-read, every notification you glance at, every five-second check of your phone costs something. Not much individually. But by 2 PM, you've spent so much bandwidth on consumption that there's nothing left for creation.

Boredom gives it back.

The Relapse

I lasted until 3 PM.

A build failed, I got frustrated, and before I made a conscious decision, my phone was in my hand. I didn't even remember opening the drawer. I was three tweets deep before I realized what had happened.

This is the part that the productivity advice never covers. The relapse isn't dramatic. It's not a moment of weakness. It's automatic. Your hand reaches, your thumb scrolls, and five minutes evaporate. You don't decide to break the streak. The streak breaks itself, and you notice after the fact.

I put the phone back. But the damage was real. Not the five minutes of scrolling. The twenty minutes after, where my brain was buzzing with fragments of other people's opinions instead of processing my own problems. The mental bandwidth I'd been carefully preserving all morning, gone in one reflexive grab.

That's the cost people underestimate. It's not the time. It's the residue. One glance at your phone leaves traces that take twenty minutes to clear. Your brain can't just switch back to deep work after seeing a notification, a headline, a message preview. It's chewing on that input whether you want it to or not.

What I Do Now

I didn't become someone who stares at walls every day. That's not realistic, and I don't think it needs to be.

What I changed: breaks are now breaks. Not "breaks where I check a different screen." When I step away from code, I step away from all screens. I make coffee without a podcast. I eat lunch without a feed. I let the compile finish without reaching for my phone.

Some days I manage it for the full day. Most days I manage it until mid-afternoon. The difference is noticeable either way. The mornings where I protect my bandwidth feel different from the mornings where I don't. Not motivated, exactly. Clearer. Like the problem I'm working on has more room to breathe.

The bugs get solved faster on those days. Not because I work harder. Because I have more brain left to work with.

I think the reason this works is embarrassingly simple. Your brain needs empty space to process what it already has. We've filled every gap with content, and then we wonder why we can't focus, why we feel scattered, why the hard problems never get solved during work hours but sometimes get solved in the shower.

The shower works because it's the only place left where you're alone with your thoughts.

Try giving yourself one more place. Tomorrow, take your first break without your phone. Five minutes. Stare out the window. Notice what your brain does when it has nothing to consume.

You might not like the first minute. But something useful will happen in the third.

This is part of an ongoing series about building as a solo developer. For the discipline side, see Why Ambitious People Stay Lazy. For what happens during the productive hours, see Shipping ML Models on macOS.