Rest Is Not Laziness

Fair warning: personal post. No productivity hack. No leadership lesson with a bow on top. Just something I had to learn the hard way.

I used to think rest was laziness.

Not consciously, of course. I would never have said it like that. I would have used better words. Discipline. Drive. Responsibility. Commitment. Momentum. All the nice words people use when they do not want to admit that they have built a life where stopping feels dangerous.

But the truth is simple: for a long time, I did not know how to stop.

If I was awake, I was available. If something broke, I was there. If someone needed an answer, I gave one. If there was a problem, I carried it around in my head until it either got solved or became part of the furniture.

At some point the job was no longer something I did.

It was where I lived.

People talk about work-life balance as if there are only two parts. Work and life. Clean separation. Nice little diagram. Close the laptop, open the front door, become a different person.

That was never how it worked for me.

I had my normal life. The one with family, responsibilities, conversations at the kitchen table, bills, school runs, birthdays, the ordinary things that should be the centre of gravity.

Then I had another life. The private escape. The emotional side channel. The place where I could be someone else for a moment, or at least not the version of myself that was already overloaded.

And then there was the third life: the job.

The job followed me everywhere. Into dinner. Into bed. Into holidays. Into weekends. Into every silence where a normal person might have heard their own breathing. I carried tickets, outages, customer expectations, technical debt, unfinished promises, and all the invisible pressure that comes with being the person who is supposed to know what to do.

Twenty hours a day is not an exaggeration when the work keeps running inside your head after the screen is off.

That is the part people miss.

You can close the laptop and still be at work.

In 2011, I crashed.

I am not going to dress that up. I nearly did not make it. That sentence is still strange to write, even after all these years.

There was no single dramatic reason. That would almost be easier. There was just accumulation. Too many lives. Too much pressure. Too much pretending. Too much being needed in places where I had no room left to be human.

And the worst part is that from the outside, it probably still looked like functioning.

That is what scares me today when I see people running the same pattern. They are praised for being reliable. For answering fast. For always delivering. For owning everything. For being intense, driven, available, sharp, useful.

Nobody asks what it costs until the invoice arrives.

And when it arrives, it does not arrive politely.

Even now, rest does not always feel natural to me.

Sometimes it still feels suspicious.

If I sit down without a task, some part of my brain starts looking for danger. What did I forget? Who is waiting? What could I build? What could I fix? What is slipping because I am not moving?

That is not ambition. Not really.

That is a nervous system that learned to confuse motion with safety.

And in tech, that confusion gets rewarded. Especially in infrastructure. Something is always broken somewhere. Something can always be improved. There is always a better design, a cleaner migration, a pending firmware upgrade, a customer waiting, a network graph that does not look right, a backlog that quietly reproduces overnight.

If your identity is built around being useful, infrastructure is a dangerous place to hide.

Because it will always give you another reason not to stop.

The hard part is not taking a day off.

The hard part is believing you are still allowed to exist when you are not producing anything.

That sounds dramatic, but I think many people know exactly what I mean.

There is a strange guilt in doing nothing when you know you could be fixing something. There is guilt in being with your family while part of your brain is still monitoring the invisible dashboard. There is guilt in resting before everything is done, because everything is never done.

So we lie to ourselves.

We say family is priority one, and then we give them the exhausted leftovers. We say health matters, and then we treat sleep like a negotiable feature. We say we are taking a break, and then we keep one eye on Slack, mail, alerts, commits, dashboards, messages.

We do not rest.

We idle with the engine running.

I wish I could say I solved this.

I have not.

But I recognize the smell earlier now.

The "just one more thing" smell. The moment where curiosity turns into compulsion. The moment where work stops feeling like work and starts feeling like oxygen. The moment where I am physically present but mentally three rooms away.

That is usually the point where I need to stop, even if stopping feels wrong.

Especially then.

Rest, for me, is not a spa day. It is not a wellness quote. It is not pretending everything is calm.

Rest is sometimes sitting with the discomfort of not being useful for a few hours.

Rest is letting the idea wait until tomorrow.

Rest is not answering immediately.

Rest is going for a walk without turning it into a strategy session.

Rest is being with my family without treating them like an interruption.

Rest is remembering that the people who love me do not need another version of me that shipped more.

They need me actually there.

The uncomfortable truth is that I still love the work.

That is what makes it complicated.

I am not trying to escape a job I hate. I am trying to survive a job, a field, and a way of thinking that can consume me because I genuinely care about it.

That is harder to explain.

When you hate something, leaving is simple in theory. Painful, maybe, but conceptually simple.

When you love something that is also capable of eating you alive, the line is harder to see.

For me, the line is usually this: if the work makes me more alive, good. If the work starts replacing life itself, dangerous.

I have crossed that line before.

I know where it leads.

There is no heroic ending here.

I still overdo it. I still get pulled into loops. I still have days where my brain wants to sprint long after the rest of me has already filed a complaint.

But I am trying to stop treating rest like failure.

Because rest is not laziness.

Rest is maintenance.

And if you work in infrastructure, you already know what happens to systems that never get maintained.