The Mental Cost of Always Being On as a Developer

## It Started With Just One Thing Last month, I closed my laptop at 11 PM. Then I opened it again at 11:15. Just to check one thing. Then at midnight — a Slack message I *might* have missed. Then at 1 AM — a GitHub notification that could have waited until morning. Could have. But I told myself it couldn't. I wasn't fixing a critical bug. I wasn't shipping a feature. I wasn't even being productive. I was just... on. Waiting. For what? I genuinely didn't know. A notification. A message. Something that would make me feel like the day wasn't wasted. The scary part? That wasn't a bad night. That was a Tuesday. If you're reading this and nodding — this one's for you. --- ## What Always On Actually Looks Like We throw this phrase around a lot, but let's get specific. Because "always on" doesn't announce itself. It creeps in slowly until it just feels normal. Here's what it actually looks like: | Sign | What It Looks Like | |------|-------------------| | Laptop never fully closes | Sleep mode is just screen off — you're back in 10 minutes | | Phone has no real off mode | You check it even on silent, even at dinner | | Vacation means slower work | Just in case" becomes your most-used phrase | | Code follows you to sleep | Literally dreaming in syntax, waking up with solutions | | Free time feels like guilt | Resting = wasted time = falling behind | The worst part? Most of us wear this as a badge. "I'm so busy." "I'm always grinding. I haven't taken a day off in months. We treat exhaustion like an achievement. --- ## The Invisible Cost Nobody Talks About This is the part most productivity articles skip. They jump straight to solutions. But if you don't understand what "always on" is actually costing you — you'll never feel the urgency to change it. ### The Physical Cost It starts with small things. Your back hurts — you blame your chair. Your eyes strain by 3 PM — you buy a blue light filter. Headaches become normal. Sleep becomes shallow. You lie down, but your brain doesn't. Then you stop exercising because "there's no time." Then you stop cooking because "there's no energy." Your body starts running on caffeine and convenience food, and somehow you're surprised when you crash every Friday evening. This isn't dramatic. This is what slow physical decline looks like when you're too busy to notice. ### The Social Cost Relationships don't end loudly when you're always on. They just... fade. Friends stop inviting you because you always cancel or show up distracted. Your family gets used to you being "there but not there" — physically in the room, mentally still in a pull request. Your partner stops telling you about their day because they can see your eyes glazing over, your hand drifting toward your phone. The loneliest I've ever felt wasn't when I was alone. It was when I was surrounded by people — and still mentally at my desk. ### The Creative Cost Here's the irony nobody warns you about: the more hours you put in, the worse your work gets. I used to think grinding through a bug was the answer. Stay longer, try harder, push through. But some of my worst code was written after hour 10. Some of my best ideas came on a morning walk when I wasn't trying at all. Your brain needs rest to make connections. It needs boredom to be creative. When you're always on, you're running on fumes and calling it productivity. You're moving fast but going nowhere. ### The Identity Cost This one hit me the hardest. At some point, I realized I had become *only* a developer. Not a person who develops software — a developer, full stop. When someone asked "what do you do for fun?" I'd pause too long. When I tried to think of a hobby, I'd draw a blank. I had optimized myself so completely for work that there was nothing left outside of it. No curiosity for things that didn't directly make me better at my job. No space for things that were just... enjoyable. I had become very good at one thing. And very boring at everything else. --- ## Why We Do This to Ourselves This isn't a personal failing. The system is designed this way. But understanding *why* we stay "always on" is the first step to changing it. | Reason | What It Actually Sounds Like | |--------|------------------------------| | Imposter syndrome | If I stop, someone will realize I'm not good enough | | Hustle culture | The grind is how you get ahead. Everyone says so. | | Remote work blur | The office is always open when the office is your bedroom | | Notification design | Apps are literally engineered to pull you back | | FOMO in a fast industry | AI is moving so fast — what if I miss something critical? | None of these are imaginary. They're real pressures. But they're also levers being pulled on you by something external — and you're allowed to stop letting them work. --- ## The Moment I Realized Something Had to Change I didn't have a dramatic breakdown. I wish I could tell you I did — it would make a cleaner story. Instead, it was a quiet moment. My partner asked me something simple. I can't even remember what it was. A normal question. And I looked at them, opened my mouth — and realized my brain was still somewhere else entirely. Still debugging. Still in a Slack thread. Still at work. I was sitting right there. And I was completely absent. That was the moment. Not a health scare, not a missed deadline, not a burnout collapse. Just a quiet, humiliating realization: I had been so busy being "always on" that I had become fully unavailable to my own life. Being on all the time wasn't making me better at anything. It was making me less present for everything that actually mattered. --- ## What Actually Changed — Honest Version I'm not going to give you a 10-step system. Because that's not what happened. What happened was messy, slow, and full of backsliding. But here's what genuinely moved the needle: **A real shutdown ritual.** Not just closing the laptop — an actual signal to my brain that work is done. For me it was making tea, putting the laptop in another room, and spending 10 minutes doing nothing. Sounds stupid. Changed everything. **Physical distance from my phone.** I started charging it outside the bedroom. I lost probably 2 hours of late-night doomscrolling immediately. My sleep improved within a week. **Blocking "off" time like a meeting.** If it's not on the calendar, it doesn't happen. I blocked Sunday mornings. Non-negotiable. The world did not end. **Accepting that some days are just okay.** Not every day has to be a 10/10 output day. Some days you do less. That's not failure — that's sustainable. **Finding something that has nothing to do with tech.** For me it was cooking. Not because it made me more productive. Not because it taught me anything transferable. Just because I liked it. That was enough of a reason. Here's what I want you to know: none of this stuck immediately. I relapsed constantly. There were weeks I was right back to opening my laptop at 11 PM "just to check one thing." The goal was never perfection. The goal was catching myself faster each time. --- ## The Hard Truth No article is going to fix this for you. Not this one. Not any other. The system that keeps you "always on" is powerful. It's built into your tools, your culture, your identity. Changing it means swimming against a current and some days you'll get swept back. You will relapse. You will have weeks that feel exactly like before. You will catch yourself checking Slack on a Sunday morning and feel ashamed. That's not failure. That's just how change works. The goal isn't to become someone who is perfectly balanced and never overworks. The goal is to stop mistaking exhaustion for ambition. To notice the cost before it becomes a crisis. To choose even occasionally, even imperfectly to be present for your own life. That's it. That's the whole thing. --- ## Before You Close This Tab When was the last time you truly disconnected? No laptop, no phone, no "just checking one thing." No guilt about not being productive. If you can't remember that's worth sitting with for a moment. And if you're in the middle of this right now — if you recognized yourself somewhere in this article I'd genuinely love to hear about it. What's the hardest part for you? What's helped, even a little? What does always on cost you that you haven't said out loud yet? Let's talk in the comments. I think we all need to hear each other on this one. --- *If this resonated, consider sharing it with a developer friend who needs to read it. Sometimes the most helpful thing is knowing you're not the only one.* --- I used AI to help structure and organize my thoughts — but every experience, feeling, and word in this article is my own.