Do Developers Ever Really Disconnect?

Every year, around the time I'm about to take a few days off, the same questions come up. Should I bring the laptop? What if I get a good idea for that side project? Is it bad to push a small commit while I'm at the beach?

These aren't just personal anxieties. They reflect something specific about being a software developer. Our work and our curiosity often live in the same place, and it's hard to know where one ends and the other begins.

The problem with "just checking in"

There's research on this. A UGA meta-analysis of 32 studies from nine countries found that employees who psychologically disengaged from work during vacation saw the most improvement in their well-being. The researchers put it simply:

If you're not at work but you're thinking about work on vacation, you might as well be at the office.

And that's the trap. Lying on a beach while your brain is halfway through a refactoring plan doesn't count as rest. The parasympathetic nervous system, the part responsible for actual recovery, can't activate properly when you're in a state of low-level alertness. It's not about where your body is. It's about where your attention goes.

A more recent survey found that those who fully disconnect report higher well-being and lower burnout compared to those who "planned to work just a little." The group that fully disconnected was, unfortunately, the smallest one.

The side project question

This is where developers tend to overthink things.

For most of us, the side project isn't just a project. It's the place we go to learn freely, build without constraints, and feel like ourselves outside of tickets and stand-ups. Calling it "work" misses the point. But calling it "rest" might miss it too.

The honest answer is: it depends on why you're doing it.

If you open your laptop on vacation because you genuinely want to, and there's no guilt, no obligation, and no one waiting on the other end, that's probably fine. Some people find flow states restorative. Some people are introverts who recharge by solving problems alone.

But if you open the laptop because you feel like you should, because staying sharp feels like a duty, because the GitHub graph gives you anxiety, then you're not resting. You're performing productivity on your own time.

The healthiest developers I know outside of work have something to say about this. They don't frame it as discipline. They frame it as knowing what actually recharges them.

What actually helps

Physical disconnection helps more than willpower. Leaving the laptop at home sounds obvious, but it changes things. Deciding not to use it isn't the same as not having it available. The decision cost adds up.

The days before and after matter. Giving yourself a day to wind down before vacation, and a day to readjust after, reduces the stress spike that undermines the whole thing. Coming back to 300 unread messages on your first morning erases a week of rest in about 20 minutes.

Full detachment isn't the only option. Some people do better with designated offline hours rather than a complete shutdown. What matters is that those hours are real, not negotiable, and not filled with passive scrolling.

Non-coding activities do something different. Walking, cooking, swimming, reading fiction, spending time with people you like. These aren't just distractions. They engage different cognitive systems and give the problem-solving part of your brain a chance to idle. Interestingly, that idle state is often when good ideas surface, not when you're chasing them.

My own take

Last year I ran a small experiment. I shut off the internet for a week. No laptop, no work-related reading, barely even the phone. I didn't go anywhere, I stayed home. And it was fine, actually good, for the first couple of days.

Then something interesting happened. Around day three or four, I started missing it. Not in a withdrawal kind of way, but genuinely. I missed reading about things I was curious about. I missed having a problem to think through. I missed the work.

I don't think that's a warning sign. I think it's information.

Two or three days of full disconnection does something real for me. It resets a kind of baseline tension I didn't know I was carrying. But beyond that, the absence starts to feel like a void I'm not sure I want to fill with anything else. Maybe I haven't found what would fill it better. Or maybe I just actually like this.

There's a version of "I love my work" that's healthy, and a version that's avoidance. I'm not always sure which one I'm in. But I've stopped treating the urge to read a tech article or think through a problem as something to be corrected. The question I ask now is simpler: am I doing this because I want to, or because I don't know how to stop?

Those two feel different when you pay attention.

I write about Ruby, Rails, and software development every Thursday. You can follow me at enderahmetyurt.com.