Presence Over Commits: Time Management for Dads in the Agentic Era
I got the flu in early February. Slept for three days straight. When I came back online, it felt like I’d time-warped into some unknown timeline — repos had advanced, model updates had shipped, new tooling had appeared. I’d missed nothing truly critical. The world hadn’t ended. And I felt genuinely rested for the first time in months.
That forced disconnection showed me something I’d been ignoring.
The Thread That Started This Post
Ryan Carson posted this morning about his agentic system running overnight, merging PRs, hitting unexpected issues, creating a backlog ticket in Linear and documenting it — without him touching anything.
His response: “Holy shit.”
Maziyar Panahi replied: “You look tired. The closer AGI feels, the less we sleep and more we lock in.”
Ryan confirmed: “I am tired. Never slept so little in my life.”
This is the moment we’re in. And I get it — these are genuinely the most exciting two years of my 20-year career. Every week something ships that redraws the map. The pull to stay locked in is real and it is rational given what’s actually happening.
But I have two young boys. My wife. A 40-hour-a-week job. And a home lab that runs OpenCastor on a Raspberry Pi at all hours.
Those two hours between when the kids go down (around 9) and when I need to be in bed (11 at the latest) — those are everything. That’s my building time. And I’ve been letting those two hours bleed into four, then six, then “just one more PR” until it’s 1am and I’m checking agent statuses on my phone while my family sleeps.
That’s not sustainable. And more importantly — it’s the wrong priority order.
Presence with your family is always the main objective. Not the latest push commit results.
What’s Actually Happening
New tools require new patterns. We haven’t built those patterns yet.
The previous era of software development had natural stopping points. You’d push code, CI would run, you’d come back in the morning. There was friction. Waiting was built in.
Agentic systems removed the friction. Now your repo is alive at 3am. Agents are filing issues, merging PRs, writing tests, pushing documentation. There’s always something to check. The notification surface is infinite.
The problem isn’t the tools. The tools are extraordinary. The problem is that we’re applying 2023 attention habits to 2026 infrastructure.
When Ryan’s Symphony agent created a Linear ticket at 2am — that’s incredible. But Ryan didn’t need to be awake to see it happen. He could have read that ticket with his coffee the next morning, well-rested, and made a better decision about it.
The agentic era doesn’t require your constant attention. It rewards your thoughtful attention. Those are different things.
The Phone Problem
Here’s the specific trap: agentic workflows are async by design, but we’re treating them as synchronous by habit.
CI passes. You get a notification. You pick up your phone. It’s 10:45pm. The kids are asleep. You’re technically present in the house, but you’ve just left the room mentally. Your partner is next to you on the couch and you’re reading a GitHub Actions summary.
You’re not building. You’re monitoring. And monitoring is a compulsion, not a strategy.
The pattern creeps in gradually. First it’s just checking if the release workflow succeeded. Then it’s reading the PR diff. Then it’s leaving a comment. Then it’s opening the laptop because “I just want to fix this one thing.” Then it’s midnight.
New tooling, same dopamine loop. We need to short-circuit it intentionally.
Building a Clean Off-Hours System
The goal is simple: let the machines work while you’re present, and be genuinely informed when you return — not perpetually half-informed while you should be sleeping or parenting.
Here’s what I’ve been building toward:
1. Set hard windows, not soft intentions
Define your building hours explicitly. Mine are roughly 9–11pm on weekdays. That’s it. Outside those windows, I’m a husband and a dad — not an engineer.
The key shift: your phone doesn’t go to the home lab after 11. It charges in another room. This sounds obvious. It is obvious. Do it anyway.
2. Configure your agents to summarize, not notify
Most notification pipelines are set up for instant alerts. Flip that. Instead of “ping me when CI passes,” configure a nightly summary: everything that ran today, what succeeded, what needs attention tomorrow.
With OpenCastor I have a nightly cron at 11:30pm that generates a daily log of everything the Pi did — commits across repos, agent sessions, OAK-D captures, what shipped. I read that log the next morning like reading a colleague’s standup. One read, full picture, no constant monitoring required.
The key principle: batch your awareness, don’t stream it.
3. Design for async handoffs, not live supervision
When you kick off an agent run before bed, it should be able to handle the next N steps without you. If your workflow requires you to approve every step, you’ll be up until it finishes.
Structure your agent tasks so they run to completion and create a clear artifact for your review — a PR, a summary doc, a filed issue — rather than pinging you mid-process. Teach your system to bring you results, not progress updates.
Ryan’s Symphony agent didn’t wake him up when it hit the unexpected codebase issue. It documented it and moved on. That’s the right design. You want your agents filing work orders for morning-you, not interrupting night-you.
4. The “push and close the laptop” rule
When you finish your building window, push what you have, start whatever background jobs make sense for overnight, and close the laptop. Don’t stay up monitoring the first 10 minutes of a run you won’t finish watching anyway.
If you’ve designed step 3 correctly, you don’t need to watch. Morning-you will have everything they need.
5. Phone-free first two hours with the kids
This one’s for the parents. Whenever you get home or the morning routine starts — two hours, phone face-down or in another room. Nothing from the lab bleeds into that window.
Two things happen: you’re actually present (kids notice, partners notice, you notice), and you get a real break from the monitoring loop. Brains need that context switch. You come back to the lab sharper because you genuinely left it for a bit.
On Not Falling Behind
Maziyar’s reply to my “take a 5-day vacation” suggestion: “Nooooo! We’ll fall behind for 3 months easy!”
I understand the feeling. But I think we’re overestimating how much active monitoring actually contributes versus how much it just feels productive.
The field is moving fast. But most of what ships in a given week is infrastructure you’ll adopt over months, not decisions that require same-day action. The synthesis work — figuring out how new tools fit your architecture, what’s worth adopting, what’s noise — that requires a clear head more than it requires being first.
You cannot out-information your way to clarity. Sleep is the thing that actually does synthesis. The brain consolidates while you’re unconscious. The engineer who slept eight hours will outperform the one who read release notes until 2am, and that gap compounds.
Staying current matters. Staying sleepless doesn’t.
What 72 Hours Does to Your Brain
Before we get to the phone settings, there’s a study worth knowing about.
Heidelberg University Hospital ran an experiment with 25 regular smartphone users. They restricted phone use for 72 hours — only essential calls and work. Then they did brain scans.
The researchers used a technique called cue-reactivity: showing participants images of turned-on smartphones alongside neutral objects, measuring how the brain responds. It’s the same method used to study substance dependency.
After just three days, activity in the nucleus accumbens and anterior cingulate cortex — the brain’s reward and self-control centers — had measurably increased, a pattern the researchers described as heightened cue-reactivity, similar to what’s observed in substance dependency studies. Activity dropped in regions involved in attention and visual processing.
First author Mike M. Schmitgen (with senior co-author Robert Christian Wolf): “Even a short break from smartphone use can lead to changes in brain activity, particularly in regions associated with reward and self-control.”
Three days. Brain scans changed.
The study didn’t require cold turkey. It required restriction. The takeaway from the researchers: your brain responds to boundaries. Even small ones. Even short periods.
Plan a 3-Day Phone Detox
If the neuroscience is right about 72 hours, then a long weekend away from the screen is genuinely meaningful — not just a feel-good gesture.
Here’s the specific plan: book a physical trip. Somewhere you have to drive to or fly to. Hotel, cabin, camping, doesn’t matter. The point is the physical distance from your home lab and your normal environment.
Before you leave:
- Kick off any long-running agent jobs that can run unattended through the weekend
- Tell collaborators you’re offline
- Set a GitHub status: Away until [date]
- Configure your nightly agent cron to keep logging (you’ll read the summary when you’re back)
At the destination:
- Put the phone in the hotel safe or the bottom of your bag
- It stays there unless there’s a genuine emergency
- For true emergencies, your partner has their phone. Your friends have phones. The hotel has a phone. You are reachable — you’re just not browsing
- If you’re traveling with family, this is actually easier: the kids will fill every hour
What you’ll notice by hour 48: the reflex pickup urge starts fading. By hour 72, you’ll forget the phone exists for stretches of time. That’s not willpower — that’s your brain literally recalibrating, the same thing the researchers measured.
You won’t fall behind by three days. I promise.
The Phone Setup That Actually Helps
The vacation is the reset. But you need a permanent configuration for the other 362 days. The goal is making the phone less interesting at the OS level — no third-party apps required, just using what’s already built in.
Both iOS and Android ship with everything you need. Third-party apps can reinforce these patterns, but the most durable changes are the ones baked into the operating system itself — they’re harder to impulsively override.
Here’s the configuration, with iOS paths and Android equivalents:
Step 1: Look at your pickups first
iOS: Screen Time → See All Activity → Pickups
Android: Digital Wellbeing → Dashboard → Unlocks
Before changing anything, look at that number. Most engineers in this era are north of 80 pickups per day. Many are over 100.
That’s the real metric. Not hours on one specific app — the pickup reflex itself. Every unconscious reach for the phone reinforces the habit. You want to shrink this number.
Step 2: Set a restrictions passcode
iOS: Settings → Screen Time → Use Screen Time Passcode
Android: Settings → Digital Wellbeing → Parental Controls (or use Wellbeing’s Focus mode lock)
Set it to something you don’t have memorized. Write it down somewhere inconvenient. The point is friction — enough that bypassing your own limits requires a deliberate choice, not a reflex.
Step 3: App time limits
iOS: Screen Time → App Limits → Add Limit
Android: Digital Wellbeing → Dashboard → tap any app → set timer
Set limits by category, not individual apps. On iOS, the Social Networking category covers X, Instagram, Bluesky, Threads, all at once. One limit, all of them. 20 minutes/day is a reasonable starting point.
When you hit the limit, the app locks. With the passcode set, bypassing it takes deliberate effort — enough to ask yourself whether you actually meant to do this.
Step 4: Scheduled downtime
iOS: Screen Time → Downtime → set your sleep window
Android: Digital Wellbeing → Bedtime Mode (schedules grayscale + Do Not Disturb + screen dim automatically)
This is the highest-leverage single setting. The phone becomes boring at 11pm and stays that way until morning. Only your allow-listed apps work — Phone, Messages, maybe a reading or meditation app. Nothing that connects you to your codebase.
Android’s Bedtime Mode goes further: it can automatically enable grayscale, Do Not Disturb, and dim the screen on a schedule without you touching anything.
Step 5: Go grayscale
iOS: Settings → Accessibility → Display & Text Size → Color Filters → Grayscale
Set up a shortcut: Settings → Accessibility → Accessibility Shortcut → Color Filters, then triple-click the side button to toggle
Android: Settings → Digital Wellbeing → Bedtime Mode (enables automatically on schedule), or Settings → Accessibility → Color and Motion → Color Correction → Grayscale for manual always-on
Every social app’s visual design is optimized to hold your attention. The red notification dots, the brand colors, the high-contrast UI — none of that is accidental. Grayscale removes the visual reward signal. The apps still function, they just look like a 1990s Palm Pilot. The urge to keep scrolling drops noticeably.
Run it from your downtime start through the morning. During focused building hours you don’t need it — you’re already locked in. It’s specifically for the couch, the bedroom, the in-between moments when the reflex fires.
Step 6: Notification audit — be ruthless
iOS: Settings → Notifications → go app by app
Android: Settings → Notifications → App Notifications → go app by app
For every app: does this need to interrupt me?
GitHub, CI systems, Slack, monitoring tools — all of it goes to badge only. No banners, no lock screen, no sounds. You’ll see the badge when you open the app intentionally. You won’t get yanked out of bedtime with your kids because a deployment finished.
The only things allowed to interrupt you at any hour: direct calls from family. Everything else waits.
What to measure
After one week, check three numbers:
- Daily pickups — target 30–50% reduction in the first week
- Social networking daily time — should be at or under your limit on most days
- First pickup of the day — what time? If it’s before coffee and before talking to your family, that’s the next thing to change
The goal isn’t zero. It’s intentional. Pick up the phone because you decided to — not because your hand moved before your brain did.
The Big Picture
Ryan ended the thread with: “Wild time to be alive. It’s actually more challenging than ever to be present with the fam. I’m working at this but not doing great right now.”
That’s honest. Most of us aren’t doing great at it right now. The tools are brand new, the patterns are still being figured out, and the pull of what’s shipping is genuinely strong.
But the kids aren’t going to be young again. The 9pm–11pm window is yours because your family trusts you to come back when it ends. That trust is worth protecting more than any release cycle.
Presence over commits. Every time.
I’m Craig Merry — building OpenCastor, RCAN, and LiveCaptionsXR on a Raspberry Pi 5 in the margins of a full-time job and a full-time family. The Pi runs at night. I do not.