For the first two years of working remotely, I didn't have a 6pm. I had "a moment when I stopped actively working but kept thinking about work until I fell asleep." It's not sustainable. It's not productive. And in my case, it wasn't even necessary — it was a dysfunctional habit dressed up as dedication.
This is the system I use now to genuinely disconnect. It's not inspirational. It's specific and it took me time to build.
Why Disconnecting Is Hard as a Remote Developer
There's a unique problem with remote work in development: the mental context of the problem you're solving doesn't disappear when you close your laptop.
Your brain keeps doing background processing. The bug you couldn't solve at 5:30pm will keep running somewhere in your cognitive system while you eat dinner. That's not inherently bad — sometimes the solution appears in the shower. The problem is when that processing has no stopping point and contaminates all the time that isn't work.
The solution isn't "stop thinking about work." It's creating conditions that signal to your brain that work mode is over.
The End-of-Day as a Ritual
The most important thing I learned is that the end of work needs to be an event, not a fade out.
My closing ritual has concrete steps and I always do them in the same order:
- Commit or stash work in progress. Leaving unsaved code is a cognitive pending item that floats.
- Update my task list for tomorrow. Write down the three priority things for the next day. This takes those pending items out of my head and puts them in an external system.
- Close all work tabs. Literally. GitHub, Linear, Slack, the project in VS Code. All closed.
- Mute work notifications on my phone. Not off — muted. That distinction matters: if there's a real emergency, someone can call.
- Leave the work room. I have a physical space dedicated to work. Leaving it is the physical closing signal.
The ritual takes 10 minutes. The first few months it felt forced. Now it's automatic and it works.
The Active Transition
After the closing ritual, I need an activity that requires real attention and isn't work-related. Not passive screens — something with a bit of mental participation.
For me that's exercise (30-45 minutes of walking or gym), but it could be cooking something new, a video game that requires concentration, reading fiction, or a real conversation with someone. What doesn't work is putting Netflix on in the background while checking your phone — that's not a transition, it's limbo.
The Phone Is the Main Problem
I can close the laptop and do all my rituals perfectly. If I then pick up the phone and open Slack "just to see if anything important came in," I restarted work mode in my head.
I have two configurations on my phone:
- Work mode (until 6pm): Slack, email, Linear notifications active.
- Personal mode (6pm onwards): only calls and direct messages from people, not apps.
iOS and Android have native features for this. There's no excuse not to set it up.
What Doesn't Work
I'll be honest about what I tried that didn't work:
- "Just checking for a second": doesn't exist. Checking work after 6pm always escalates.
- Flexible hours without clear limits: "I work until I'm done" in remote development means working more hours, not fewer.
- Guilt as a motivator: feeling guilty for not working more didn't make me more productive. It made me more anxious and equally unproductive.
The Real Result
I work better during my working hours because I know they have a limit. I have more energy in the morning because I genuinely rested at night. And difficult technical problems I solve more often in the first hour of the morning than at 10pm, when I'm exhausted and forcing it.
Disconnecting isn't laziness. It's system maintenance.