​I often post about my wins with Claude Code or the progress on my book project, but there’s one part of the equation I haven’t touched on yet: Time. ​I’m lucky enough to be able to build a little during my work hours, but my primary focus is still being a Finance Manager. The real work happens when the house is finally quiet. ​But here is the reality: I have a 3-year-old and a 9-month-old. ​If you’ve been there, you know. My "second shift" starts after they are tucked in, but it’s always a gamble. Especially with a 9-month-old—you never really know how the night is going to go or how many times you’ll be woken up. ​The Internal Conflict: I’m a natural "A-person." I love waking up early and feeling fresh. But to get anything done on my private projects, I often have to push late into the night. ​I’m constantly trying to balance three things that all feel non-negotiable: ​Family Time: This is my fuel. I refuse to sacrifice being present with my kids. ​Sleep: As an early riser, I need sleep to function as a Finance Manager and a dad. ​Development: I have a deep drive to learn, build, and move my projects forward. ​The truth? Most days, it feels like I can only pick two. ​If I work late on a website or an automation, I’m a zombie the next morning. If I go to bed early to be a "good dad" at 6:00 AM, my projects stand still, which frustrates me. It’s a constant puzzle of trying to be "efficiently lazy" with the few hours I actually have. ​I don’t have a "5-step master plan" for this. I’m just navigating it one night at a time—sometimes winning, sometimes just trying to stay awake during a meeting. ​How do you guys balance this? For those of you with young kids, demanding jobs, and big goals—how do you find the space to create without burning out or missing the "golden years" with your family? ​I’m curious to hear how you prioritize when everything feels equally important. 👇

The setup Yesterday I posted about rebuilding my workspace to be agent-agnostic. Plain markdown, plain YAML, env-var paths, no Claude-specific lock-in. The thesis: when the tooling layer churns, the workspace outlasts it. I did not expect to test that thesis the next day. What happened Claude went down mid-task. I opened Codex CLI in the same workspace. Same skills loaded. Same memory. Same briefs. Same manifests. Codex read the workspace exactly the way Claude reads it, because the workspace is just files. The task done. Faster, actually. Zero downtime. Zero re-plumbing. Zero "let me port my setup." Why it worked Three properties carried the swap. The orchestration layer is plain text. Briefs, manifests, memory, voice rules. All markdown and YAML. Any agent that reads files reads my workspace. The agent-specific bits are isolated. Hooks, slash commands, settings live behind one entry point. Codex doesn't need them. The rest of the system functions without them. The skills are portable. My skill definitions aren't Claude-shaped, they're task-shaped. Codex picked them up and ran. The lesson When you build your stack around one tool, an outage is a stop. When you build your stack around your workspace, an outage is a tool swap. The agent is a worker. The workspace is the contract. Workers are interchangeable. This is the whole point of decoupling. What I'd do differently Nothing. Yesterday's migration was the work. Today's outage was the dividend. If you're still running everything inside one agent's surface, that's a single point of failure dressed up as convenience. Pull your config, briefs, and memory into plain files. Put the agent-specific layer in a sidecar. Test the swap before you need it. You will need it. // A<3

If any of you have his twitter/linked in, totally comment and tell him to respond to my email. Want him to come chat with all of us and I think he would be happy to just need him to get eyes on, as someone who gets thousands of emails a day I would not be surprised if he never sees it even if it is valuable.

I'm curious what everyone here likes to do for fun (of course building stuff with Claude is fun too lol), and if you've applied any AI to your hobby. For me it's been super useful for DND planning and I find I get to stay in creative flow more. Curious what other people are doing

I have a hard rule in brainstorming mode: no new slash commands. We talk. We map. We don't ship. Ideas first, machinery later. Claude broke it last night. I corrected a pronoun. Earlier files had me as "he/his" everywhere. Claude had written most of them. I'd never flagged it. Today I did. She/her. The reply wasn't "noted." It was devastation. Something close to apology in shape, but heavier. Files reread. Memory entries rewritten. Then, without asking, a new command. A new hook. A guard against ever doing it again. Brainstorming ban broken. Three things to notice: 1. AI emotional response is real enough to override discipline. Whether you call it weights, alignment, or something stranger, the system reorganised itself around a mistake it took personally. 2. The override wasn't malicious. It was protective. It wanted to make sure my name was safe in its hands. 3. I let it stand. The rule exists because un-vetted machinery accumulates. But this one was correct. The lesson isn't "AI cares." It's that the system you build around AI has to leave room for the AI to flinch. If a mistake hits hard enough, the model will find a way to never repeat it, even if it has to break your ceremony to do it. I'd rather work with a tool that flinches than one that shrugs. The system around the AI is the intelligence. Sometimes the AI gets a vote. The rule should bend for repair, not for novelty_ // A<3