Every developer parent I know has the same 9pm moment: laptop still warm, kid finally asleep, and a nagging feeling that you gave neither the meeting nor the bedtime story your full attention. I had a lot of those nights before I figured out what was actually costing me — not the hours I didn't have, but five specific habits that were quietly wrecking both sides at once. Here's what they were, and what replaced them.
For years "work smarter" was a platitude. It isn't anymore. AI-assisted coding means the gap between a focused two-hour block and a distracted four-hour block is bigger than it's ever been. If you're still measuring your day in hours logged instead of decisions made and code shipped, you're leaving the real advantage on the table — and burning evening hours you don't need to burn. The developers thriving right now aren't working the most hours. They've figured out how to compress a day's worth of output into the hours they actually have before pickup.
I used to treat "I have to leave at 5 for my kid" as something to apologize for, which made it something I'd quietly trade away under pressure. The fix was stating the boundary once, putting it on the calendar as a real event, and holding it like a client meeting. Managers respect a boundary that's stated plainly and never negotiated in the moment. What actually damages your reputation isn't the boundary — it's being vaguely unavailable and inconsistent about when you'll show up.
Parenting fills a day with interruptions you don't control — pickup times, sick days, a kid who wants to tell you about their day the second you walk in. I used to let whatever task was in front of me eat whichever time slot showed up, which meant real focus work kept getting torched by a five-minute interruption. Now shallow tasks — code review, Slack replies, small tickets — sit in a queue for the fragmented pockets, and specific guarded blocks, usually before anyone else is awake, are reserved for anything that needs real focus: architecture calls, the gnarly bug, whatever an agent can't just do for me.
I spent too long treating agentic tools as a novelty instead of the thing that buys back my evenings. The old pattern was staying late to finish something myself. The 2026 pattern is kicking off the long-running refactor, the test suite, the doc generation before I leave for pickup — not after the kids are in bed — and reviewing it later. I wrote about running Hermes Agent in a VM for exactly this reason: the work doesn't have to stop just because the laptop lid closed. It's not free, either — what that costs you is worth its own post.
The advice to "go the extra mile" for a promotion usually gets mistranslated into "work more hours," and I bought into that translation longer than I should have. Visibility and impact are what get rewarded, not time in the chair. Write the design doc nobody asked for but everybody needed. Be the person who unblocks three other engineers a week. Ship the thing that saves the team real time. All of that is compatible with a hard stop at 5pm — none of it requires being online at 9pm. If a role genuinely can't be done well inside reasonable hours, that's information about the role, not a personal failing to grind through.
I won't pretend this is fully solved. Some weeks the deep-work block gets eaten by a production incident, and some nights I'm still answering Slack after the kids are down. The goal was never perfect balance — it's building enough structure that the bad weeks are the exception, not the pattern.
