Rest is a skill

Last night at 11:30 PM, I was still working on a new feature. Not because I had to. Because I wanted to. I woke up early, and my first thought was to keep going.

This isn't burnout. It's something harder to spot: when the work is good enough that you don't notice you're not resting.

The "one more task" trap

As a solo founder, no one sends you home. There's no team to signal that it's enough. You are the system — and the system doesn't flag when it's overheating.

The problem isn't working too much. It's that the line between work and rest becomes invisible. On earlier client projects, there were natural stopping points: handoffs, meetings, weekends. When you're working on your own thing, those don't exist.

Stanford research shows that hourly productivity drops sharply past 50 hours per week. After 55, additional output is nearly zero. But in the moment, it still feels like progress.

Rest is not a reward

Most founders treat rest as something earned. "I'll rest after we hit X revenue." "I'll take a break after launch." That moment never comes.

Rest isn't what happens after work. Rest is what makes work function. It's not a break — it's an input. It requires the same intentional design as any feature you ship.

Over time I learned that my best decisions never happen at midnight. They happen in the morning, rested, with a clear head. At night, I write code. In the morning, I make decisions.

Design it like everything else

Wanting to rest isn't enough. You have to design it — the same way you design sprints, features, and deploys.

For me, that means having a time after which I don't open the laptop. It doesn't always work. But the rule exists, and that matters. Because without structure, the default is work — especially when you enjoy it.

Elite athletes don't rest because they're tired. They rest because they know they won't improve without it. Rest isn't weakness. It's a skill.

Learn it before your body teaches it for you.