Tech moves fast. Deadlines are always tight. There's always a production issue that needs looking at. Add that to the fact that learning new technologies requires staying current, and you get a situation where work can expand to fill every waking hour if you let it. I've been there. It's easy to convince yourself that "just this one more thing" is fine, that missing a weekend won't kill you, that you can optimize for sleep later.

The problem is that it compounds. Miss a weekend once and you can recover. Miss a weekend every month and you're running on fumes. Work extended hours for a few weeks and you're fine. Work extended hours for a year and you burn out. And burned out engineers are slow, cranky, and eventually gone.

You have to decide when you stop working. Not "I'll work as long as it takes" but an actual time. And you have to actually stop. For some people that's 5 PM. For others it's 6 or 7. But there has to be a line. After that time, you're not checking Slack. You're not scrolling through GitHub. You're done.

The reason this works is that constraints force efficiency. If you know you have to stop at 6 PM, you're going to prioritize what actually matters. You're going to say no to meetings you don't need. You're going to delegate more. You're not going to waste time on things that don't move the needle.

And here's the thing: the work will still be there tomorrow. If you stopped at 6 and there's still work left, that's information. That's a sign you've got too much. Talk to your manager. Reprioritize. But don't just work more hours hoping it'll somehow fix itself.

Your brain is wired to keep thinking about problems. You'll be making dinner and suddenly remember a weird bug and want to look at it. You'll be trying to sleep and ideas will pop into your head. The trick is to give yourself time to transition. Maybe you journal about what you didn't finish so you don't have to keep it in your head. Maybe you go for a walk. Maybe you do something physical that requires focus.

A lot of people work long hours not because they have that much work, but because they're doing things that don't matter. They're trying to optimize something that won't move the needle. They're handling interrupts instead of actual work. They're in meetings about meetings. Actually look at what you're doing. Is this important? Does it directly impact the business or your users or your team?

Sitting at your desk grinding for eight hours straight makes you slower and dumber, not faster and smarter. Breaks are when your brain actually consolidates information and solves problems in the background. Take a actual breaks during the day. Stand up. Walk around. Look at something that's not your monitor.

Technology changes fast and you have to stay current. That's real. But you can't do it on top of full-time work and a personal life. You have to choose. Either you allocate real time during work for learning, or you accept that your learning happens slowly, or you decide that right now you're just maintaining and you'll get back to aggressive learning later.

Half the problem is that your manager doesn't know you're drowning until you quit. Tell them. "I'm working 55 hours a week and I'm not sustainable at this pace. Here's what I could do to improve: prioritize the project, defer some work, hire another engineer, reduce meetings." Give them the problem and some solutions.

You'll be tempted to cut exercise and sleep when you're busy. Don't. A well-rested engineer who exercises regularly will accomplish more in 40 focused hours than a burned-out engineer will accomplish in 60 scattered hours. Make these non-negotiable.

Sometimes the problem is the job itself. You can do all this stuff and if the job itself requires sixty hour weeks, you're still not achieving balance. Some companies and projects are just structured that way. Early stage startups, high growth companies, companies with unrealistic timelines.

The goal isn't to work as little as possible. It's to have energy left over after work. Energy for relationships, for hobbies, for learning things outside of tech, for just existing as a human instead of as a robot. When you have that, work is better too. You're more creative. You're more resilient. You actually care about what you're building.