(not proof read - sorry for all the grammar mistakes xD)

The Tagline That Became Real

For a while now, my LinkedIn tagline has been something along the lines of:

“stay at home parent by day, game dev by nap time”

It sounded good. It described what I wanted to be doing. But if I am being honest… it was more of an aspiration than reality.

We have a nanny who helps us a few days during the week, but I still take care of the infinite home improvements, cooking breakfast, lunch, and dinner, cleaning and tidying up the house. All of that meant that doing any sort of dev work was really hard. Sometimes it meant bringing my noisy laptop to my daughter’s room, or being away in another room keeping an eye on her via the baby monitor. Not ideal.

But something changed.

A Workflow That Worked… But Wasn’t Great

I started noticing a pattern in how I was spending my mental cycles.

While doing chores, while waiting for my daughter to fall asleep… my mind would wander to code.

• “What if I structured the system this way?”
• “That bug is probably happening because of X”
• “The architecture should really be Y instead of Z”

The thinking about code was happening. The designing was happening.

I started writing notes on my phone. System designs. Architecture decisions. Feature ideas.

Whenever I had time, I would take these notes to my computer, copy them over, organize them into tasks, use LLM agents to do initial prototypes and some feature work.

That workflow worked. It was fine. But it was also a waste of time - all that transferring and organizing and context switching.

That workflow changed once I got an initial prototype of my LLM agent-based home assistant working.

Enter Butler IO

It started with something called a “Butler’s Book”.

A Butler’s Book is essentially a book where you keep a lot of info about the house - where certain valves are, when filters need to be changed, things that need to be done every season, and so on.

I started it as a git-based project with markdown documents and then used an AI to help me brainstorm some ideas and scaffold some structure. It worked really well.

But I wanted to have access to it on the go.

So I created an app that allowed me to interface with it via my phone. I don’t like exposing ports to my home network, so I used Google Firebase as a middleware for communicating between my phone and home server.

And then I realized something…

I could point Butler to the folders where I have my dev programming projects.

Including Butler IO itself.

#FuckYeah 🎉

When Things Got Meta

All those notes I used to have to transfer over to my computer whenever I had the chance? I could now just send them straight to their own projects.

That is when I started really learning about how to create a good LLM agent structure that worked for me. One that could not only take in and organize my notes, but also implement features in my projects.

And then things got wild.

I started implementing new features on Butler through Butler itself.

Code reviews? Done through Butler. Refactoring? Done through Butler. Bug fixing? Done through Butler.

I am now at the point where I am having conversations with Butler about how to improve Butler. It is recursive. It is meta. It is wild.

Natural Language Programming

Through all of this, I have been studying and practicing different things:

• Learning Flutter and Dart
• Figuring out what agent-based workflow works well for me
• Understanding where AI shines and where it struggles

And I have come to a realization about how I approach development now:

I have transitioned to “natural language programming first” and hands-on programming second.

What does that mean?

I write very detailed designs and architectural instructions. If you have worked with me before, you know I really push for really good documentation and I am always looking for how to improve how I communicate - for myself and for my team.

It is no different with this new workflow. In fact, I think that aspect got even better - supercharged in a way.

When changing features, adding or removing them, it is a lot easier now to also change the documentation to make sure it stays relevant. Both AIs and I can reference it to plan and make changes.

This doesn’t mean I stopped coding. It means I am more intentional about when I code. The routine coding tasks? Those get delegated. The architectural decisions and tricky edge cases? Those are still mine.

Less Time on the Computer, More Time Living

Here is what this workflow has really given me:

I spend way less time on my computer now. That means more time improving myself as a husband, as a dad, and as a homemaker.

And I am still doing one of the things I have been doing throughout my whole life - coding.

Actually… I came to realize that it was not coding that I loved all along. It was creating things.

Now that I am a dad and a stay at home dad, I sort of returned to that feeling I had as a kid - where I would make games for myself and my cousins about our summer adventures.

But now? Now I am gearing up to make games for my daughter.

And I am already making games for my nephew! He is 4 years old right now. Together we made a game mode for a game I had made for him.

He looooooved it! ❤️

Soon I will be sharing these games that I have been making.

Conclusion

If you had told me a year ago that AI would make my “stay at home parent by day, game dev by nap time” tagline real… I would have been skeptical.

But here we are.

• I am parenting full time ✓
• I am a better husband, dad, and homemaker ✓
• I am making games for my family ✓
• I am creating things I love ✓

#FuckYeah

More on Butler IO later. That deserves its own post. 😉