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.
Top comments (57)
I tend to go on long walks regularly without my phone to disconnect. This post is a good reminder to take care of ourselves!
Long walks without my phone that's such a small habit with huge impact.
The fact that being unreachable for an hour feels uncomfortable says everything about how always on we've become.
Thanks for the reminder. I'm putting my phone down and going outside today. 🙌
This is honestly why I went all in on automation. I have agents monitoring my sites, my SEO, my pipelines. They ping me when something breaks. I don't ping them. Humans shouldn't be the cron job.
Humans shouldn't be the cron job I need that on a mug.
You're absolutely right. The ideal state is agents monitoring, humans getting pinged only when something breaks. That's not automation for efficiency that's automation for sanity.
But here's my honest struggle: I've built the automations. I still don't trust them. I check manually anyway. Out of habit. Out of anxiety. I don't know.
How did you cross that bridge? What made you actually stop checking?
Genuinely asking. 🙌
Honestly? I didn't decide to stop checking. I just started noticing that every time I checked manually, the agent had already caught it. After a few weeks of that, the habit faded on its own. Trust isn't a decision, it's evidence piling up until your anxiety runs out of arguments.
This is genuinely one of the most insightful things I've read in a while.
Trust isn't a decision, it's evidence piling up until your anxiety runs out of arguments.
I'm going to remember that line. Because you're right we think trust is something we choose to do. But real trust? It's not a leap of faith. It's looking at the data and realizing there's nothing left to be afraid of.
What you described checking manually and realizing the agent already got it, over and over that's not blind trust. That's informed trust. And it's the only kind that actually lasts.
I think I've been approaching it backwards. Trying to decide to trust instead of just letting the evidence accumulate. You've given me a lot to think about.
Thank you for this. Seriously. 🙌
I don't know. I've developed some kind of mechanism for opening websites and checking notifications. Even if I don't have any notifications all day, I still open the browser and type in the address. I don't know. Maybe my brain reboots. It's... weird? 🥴
You just named something I've been doing for years without realizing it.
That automatic open browser, type address, check nothing I do it too. It's not even about notifications anymore. It's just. what my hands do. Muscle memory disguised as urgency.
Maybe my brain reboots that's actually a beautiful way to frame it. A tiny reset. But also a reminder that we've trained ourselves to need these resets constantly.
Thanks for sharing this. Makes me feel less weird about it. 🙌
Does it ever feel different on days when you're actually rested?
I am trapped in this autonomy. Perhaps I have become a slave of notification.
the automatic type-the-address thing is too real. thats basically the browser version of reopening the laptop at 11:15 just to check one thing
While I can understand that there are people that have that always on feeling. I never experienced it myself.
I think there are two main reasons I never had that feeling:
So during the day that are at least two hours I'm not "on".
I think the always on mindset is a cultural problem. When the boss of a company is always on they are going to expect employees to have the same mindset.
I don't get that a lot of people don't understand work is an ultra marathon effort not a sprint. There will be some times you need to sprint, but those times will need to be compensated by down time otherwise you injure yourself.
This is a really helpful counterperspective.
You've highlighted something important: for many people, always-on isn't inevitable. It's often a symptom of missing structures. Two hours of forced off-time daily dog walks, bike commutes those create boundaries automatically.
The commute point really stands out. Remote work erased that transition for many of us. No physical separation between work and home.
And you're right about culture. When leadership models always-on, it becomes the unspoken expectation.
Sometimes the answer isn't more discipline. It's more dog walks. 🙌
Even when we were forced to work from home I still rode my bike every day for at least an hour. It has become that deep of a daily routine.
And don't get me wrong there are days I hate my bikeride or dog walk, due to weather or just not feeling that well. But even on those days I still feel that little reward that I did do it.
Even on days I hate it, I still feel that little reward that's the real secret right there.
Motivation comes and goes. Discipline is doing it anyway. And that little reward you feel? That's not nothing. That's the feeling of not letting yourself down.
The fact that you kept the bike routine during WFH that's impressive. Most of us let those structures collapse.
Thanks for sharing this. It's honest and helpful. 🙌
Seriously
This just made my day.
Coming from you that means a lot. Thank you for reading and for everything you've built with DEV. This platform has given me space to write to struggle to figure things out in public.
Genuinely grateful. 🙌
Excellent article.
About 20 years ago, I went through a burnout, followed by severe depression and a divorce. I had completely lost my sense of purpose in my work, and I felt like I was contributing to a world that didn’t resonate with me anymore.
So I made a radical change. I left tech and retrained in heritage masonry — working with old stones, as far away from computers as possible. I saw myself as a repentant software engineer, someone who had turned his back on it all.
A year ago, I bought my first computer in 20 years — just to play The Witcher 3. But I couldn’t help myself. I started looking at what was happening in tech again, the current problems, the ideas… and I fell back into it.
The difference now is that I have no specific goals, no external pressure — and no boss. I choose what I work on, when I work, and under what constraints. I only do it if I genuinely enjoy it.
And I rediscovered something I had forgotten: that intense intellectual stimulation. The feeling that every neuron in my brain is firing at once. Honestly, it feels like a powerful drug.
That said, I can still feel the patterns you describe starting to come back sometimes. When that happens, I step away and do something completely unrelated to tech, sometimes for several days.
So far, it seems to work — but I’ve learned that I need to stay vigilant with myself.
Thanks again for the great article.
Thanks for your comment.
Whenever I take a break for a few days, it has always been beneficial for my projects. I come back either with fresh ideas or with a clearer perspective. It helps me avoid getting stuck in the weeds and losing sight of what I’m actually doing.
In practice, I’ve found that I’m more productive this way.
That said, I know this kind of freedom isn’t available to everyone. I’ve lost a lot in terms of income, but I’ve gained much more in comfort and freedom.
The quality of what I produce has improved as well. I don’t think in terms of quantity anymore — haha.
And I’d also like to thank Arch again for the article — this is actually my first time commenting on a forum in 20 years.
I'm honored that my comment made you write after 20 years.
That's not nothing.
What you said about breaks making you more productive that's the wisdom most people learn too late. And your honesty about the trade-off (income vs freedom) that's rare. Most people only show the gain.
Thank you for sharing your story. And welcome back to forums. We're lucky to have you here. 🙌
This is one of the most incredible career arcs I've ever heard.
From software engineer → heritage masonry → back to tech after 20 years — and not just back, but back on your own terms. No boss. No pressure. Just the joy of "every neuron firing at once."
The fact that you left tech because it didn't resonate, worked with old stones (literally as far from computers as possible), and then came back just because you were curious that's not a comeback. That's a whole different relationship with work.
And what you said about staying vigilant that's the real wisdom. You know the patterns. You know they can come back. So you step away for days when you feel it. That's not weakness. That's hard-earned self-awareness.
"I have no specific goals, no external pressure, no boss. I only do it if I genuinely enjoy it."
That's not just a career. That's freedom.
Thank you for sharing this. I don't think I'll forget it. 🙌
the AI conversation is making this so much worse and nobody talks about it.
theres this new layer of always-on now. did you try the new model. did you read the latest benchmark. are you still relevant. its not just slack notifications anymore. its existential dread as a service.
and the people pushing that anxiety the hardest are literally raising money off your fear. the "youll be replaced" story isnt just wrong historically. its actively bad for developer mental health. setting boundaries doesnt mean falling behind.
Existential dread as a service that's the perfect phrase for this.
You're absolutely right. The always-on problem used to be Slack and late nights. Now it's AI benchmarks, model releases, and the quiet fear of being replaced. And the worst part? Someone is raising money off that fear.
Setting boundaries doesn't mean falling behind that's the lie we've internalized. But it's just good marketing for the people selling the anxiety.
Thanks for adding this. This is exactly the conversation we need to have. 🙌
Great article, and I completely resonate with the struggle you’re describing.
I’d add this: We’re not failing ourselves individually—we’re participating in a system designed to keep us enslaved. Social media is psychologically engineered like a drug. Manufacturing is designed to break right after the warranty ends. Independent thinking is practically penalized. Marketing has evolved into a guilty weapon.
The good news? We can still realize we’re on the dark side—and that awareness is the first real step.
There’s no magic bullet, just honest evaluation of our daily inputs. Thankfully, our tech brains are overtrained for this and we can refactor our daily performance. You mentioned habits—and yes, rituals are incredibly powerful weapons for reclaiming ourselves.
Let me add one more thing: purpose. Without a clear goal, habits alone won’t take us far.
For me, the goal is simple: process as many genuine smiles as possible.
Every night, I run my own evaluation: How many smiles today? No judgment. Just realization.
That healthy background daemon keeps me human in an inhuman system. Thanks for the reminder that we’re not alone in this fight... :love:
This is genuinely beautiful.
You're absolutely right we're not failing individually. We're in a system designed to keep us enslaved. Awareness is the first step but you've gone beyond awareness to actual rituals.
How many genuine smiles today? that's a metric I never knew I needed. Not lines of code. Not tasks completed. Just... smiles.
The mirror smile as a daily constructor. Recursively making family's life easier. This isn't just burnout prevention. This is a philosophy.
Thank you for sharing this. You've given me a lot to think about and at least one genuine smile today. 🙌
This is painfully relatable and also perfectly ironic.
You wanted to be lazy, so you automated, systematized, simplified. That's not laziness that's skill. But the company saw delivers and gave you more work.
The AI Agent hobby story is the sad punchline. You built something for fun, shared it with pride and got assigned a rollout project.
Work gravitates toward the people who are good at it that's the hidden tax of competence.
You're not alone in this cycle. And wanting to be lazy isn't laziness. It's wanting to breathe.
Thanks for this honest comment. 🙌
This hit uncomfortably close.
The “human cron job” metaphor is exactly it — not working, just polling life for events.
What resonated most for me is the identity part. At some point, the boundary disappears and you’re no longer someone who writes code, you are the role. That’s where it becomes dangerous.
Curious how others handle this in remote setups — do you rely more on rituals (like the shutdown routine mentioned) or hard constraints (no Slack after X PM)?
Polling life for events that's painfully accurate.
And the identity part when you stop being someone who codes and become The Developer that's where it gets dangerous. Because The Developer never clocks out.
To your question about remote setups: rituals > hard constraints for me. Hard rules (no Slack after 8 PM) I break them. But a shutdown ritual (tea, close laptop, leave the room) that actually works.
What's worked for you?
Really appreciate this comment. 🙌
Some comments may only be visible to logged-in visitors. Sign in to view all comments.