This one's a little personal. Bear with me. There's a lesson in here for every developer.
Today is my birthday. And instead of just eating cake and calling it a day, I found myself reflecting on something uncomfortable: I've been working wrong.
Not inefficiently. Not lazily. Wrong in a way that quietly erodes everything around the work itself.
The Real Problem Wasn't Overworking. It Was Being Online While Working.
I used to think the enemy was long hours. But I've realized the bigger culprit is context-switching disguised as collaboration. The back-and-forth Slack messages, the quick "got a sec?" pings, the notification that pulls you out of flow right when things are clicking.
My personal success metric has always been simple: sit in one place for one focused hour. That's it. Review PRs, write code, think deeply, but for one unbroken hour.
When I overwork, I blow past that hour. And the message that sends to my brain is: "time doesn't matter, anything can interrupt anything." That's the real damage.
The 60-Minute Rule
If you work for four uninterrupted hours without context-switching, you can build extraordinary things. But when you're in "always-on" mode, you never really start. You're perpetually warming up.
The 60-minute rule in practice:
No context switching for one hour. Silence is not a problem to solve. Back-and-forth messages are a tax on your thinking. Batch them, don't react to them.
Slow Down to Ship Better
I've been re-reading Cal Newport's Slow Productivity, and it reframed how I think about velocity. The argument isn't "work less." It's expand your time horizon.
Most of us think in days or weeks. What if you thought in 90-day windows instead?
When nothing feels urgent over a 90-day scale, you make better architectural decisions. You write more maintainable code. You mentor more. You think before you type.
The irony of AI-accelerated development is that we're shipping faster but sometimes thinking shallower. The antidote isn't slowing your hands. It's slowing your assumptions.
Reading Is Not a Luxury. It's Leverage.
When I'm overworked, reading is the first thing to go. That's backwards.
Books like Slow Productivity and Ultralearning have made me a meaningfully better developer, not by teaching me syntax, but by teaching me how to think about learning and systems. Right now I'm reading a book on Tesla. Not the car company. The man.
If you're not reading outside your stack, you're optimizing inside a box you can't see.
The Pause Is the Strategy
Leaders in tech love talking about velocity. But the best ones I've watched are masters of the pause. The deliberate moment where you stop, look at the trajectory, and ask: is this the right direction?
The pause isn't laziness. It's steering.
Without pausing, you get fast. Without direction, fast just means you arrive at the wrong place sooner.
Gym. Yoga. Breathe.
I know this feels off-topic for a dev blog. Stay with me.
Going to the gym consistently, even when it's inconvenient, builds an identity: I do hard things even when they're hard. That identity doesn't stay in the gym. It shows up when you're debugging at hour three, when you're refactoring code you hate, when you're in a meeting that's going sideways.
Deep breathing and deep thinking are more correlated than we give credit for. When your breath is shallow and reactive, so is your thinking. When you breathe deliberately, you pause deliberately.
Practical tip: 4-7-8 breathing before your focused hour. Inhale 4 counts, hold 7, exhale 8. It sounds small. It isn't.
It's Not Hardwork. It's Respect.
The most underrated skill in a dev team isn't technical. It's knowing when to speak and when to listen.
Let product managers do their job. Let managers manage. Trust the people around you to play their roles. When you stop trying to fill every gap, you free up your best thinking for the work only you can do.
Speak less. Listen more. Do your work well in the time you have.
A Birthday Checklist (For Myself, and Maybe You)
Limit deep work to 60-minute blocks and protect them fiercely. Think in 90-day windows, not today's fire. Read one non-technical book per month. Build a habit stack, like going to the gym or reading after an existing trigger such as brushing your teeth. Practice the pause before reacting. Breathe deeper, it really does help. Don't break the 60-minute rule.
Final Thought
Atomic habits. Slow productivity. Deep breathing. These aren't self-help clichés. They're systems for staying human while doing technical work that constantly tempts you toward urgency.
Make 1% improvements. Stack them. Trust the 90-day window.
And if it's your birthday too, happy birthday. Slow down. You've got time.
Thanks for reading
Top comments (0)