Why I Started Writing

I have been building things with computers for most of my life. But this past year changed everything about how I think about what building means.

I am not a Silicon Valley founder. I did not study computer science at Stanford. I am a self-taught developer in Ontario, Canada who spent years doing the kind of work that does not get written about. Help desks. Infrastructure. Troubleshooting systems that other people built and walked away from.

Then AI got good enough to work with, not just talk to. And something shifted.

What Changed

I started building systems where AI is not a feature. It is a collaborator. I have agents that monitor my business while I sleep. I have workflows that score leads, draft proposals, and flag problems before I see them. I built a personal operating system that gives me the kind of leverage that used to require a team.

None of this is theoretical. It is running right now on a VPS I maintain myself.

But here is the thing nobody talks about: the interesting part is not the technology. The interesting part is the decisions. When do you let the machine act on its own? When do you keep a human in the loop? Where is the line between automation and abdication?

What This Blog Is About

This is a blog about building at the intersection of humanity and technology.

I will write about the systems I build, but not in a way that reads like a product launch. I will write about what worked, what broke, and what I learned. I will write about the architectural choices that sound boring on paper but determine whether a system survives contact with reality.

Some of what I will cover:

• How AI agents actually coordinate. Not the marketing version. The database tables, the failure modes, the design tradeoffs.
• Automation with guardrails. What it looks like to give AI real autonomy while keeping humans in control of what matters.
• Building in public, mid-career. What it looks like to start something new when you have experience but no institutional backing.
• Infrastructure as identity. Why the systems you build reflect how you think, and why that matters more than your tech stack.

Who This Is For

If you are a developer who builds things alone or in a small team, this might resonate. If you are curious about AI but skeptical of the hype, you will find something honest here. If you are in the second half of your career and wondering whether it is too late to reinvent yourself, I can tell you it is not.

I am not going to pretend I have it figured out. I am going to document what it looks like to figure it out in real time.

That is the whole premise. No manifesto. No five-step framework. Just a builder writing about what he is building and why.

Welcome.