Why I Started Commonbound
In my lifetime, software development grew up.
What began as a niche technical craft turned into the nervous system of modern civilization. Software runs the economy, our communications, our infrastructure, our entertainment, and increasingly our thinking.
And now it sits on the edge of something new.
For the first time in history, the craft that built the digital world may be on the verge of leaving human hands and entering the mind of something far larger than us.
I’ve spent thirty years watching this happen from inside the machine.
This journal is about what comes next.
Thirty Years Inside Software
Over the past three decades I’ve had my hands in just about every corner of the software industry.
Startups.
Consulting.
My own failed ventures.
Enterprise systems.
I’ve worked as a UI architect, web architect, and today as a backend architect.
The industries changed constantly, but the pattern was always the same. If it was SaaS, I was probably involved somewhere along the line.
Mass marketing systems.
Inventory management.
Online marketplaces and sales platforms.
Music distribution.
Cloud cost management.
Fleet intelligence systems.
Dealership and service lane platforms.
Even power grid engineering software with ABB.
Along the way I helped friends and colleagues build systems in industries ranging from defense technology to radar systems.
Software became the universal layer that connects everything.
And for most of my career, building it felt like standing on the frontier.
The First Experiment
My fascination with systems started long before my career.
If you want the honest origin story, it probably started when I was a kid driving Matchbox cars through my peanut butter toast.
The world was something to experiment with.
Later, when I began learning real programming, my stepfather and I tried helping a friend who had built a horse racing odds system. Humans were setting the odds, but he had an idea: what if the math behind race outcomes could reveal patterns humans couldn’t see?
Imagine a race that starts with odds like this:
1, 2, 3
But the finish comes out:
2, 3, 1
If you collect enough data, long-shot wins begin to show patterns. You can start asking whether a long shot is “due.”
We tried to push that idea further using early neural networks and fuzzy logic systems. The goal was simple: take a cold deterministic machine and try to make it reason about uncertainty the way humans do.
It didn’t work.
For us, it was a complete failure.
But it planted something in my mind that never left.
From that moment forward, I began looking at everything through a certain lens. Not just software, but systems. Patterns. Probabilities. The hidden structures underneath the visible world.
That perspective was reinforced by another lifelong habit: reading science fiction.
A lot of it.
Sci-fi has a way of asking uncomfortable questions about the future long before the rest of society is ready to hear them.
Systems Everywhere
One thing people misunderstand about software engineers is that many of us aren’t really obsessed with computers.
We’re obsessed with systems.
The same curiosity that leads someone to write software often shows up in other parts of life.
I’ve turned every nut, bolt, screw, and wire in my Jeep.
I’ve built decks and patios with my own hands.
The physical world is just another system to understand and work with.
That’s always been the deeper motivation behind writing code.
Not screens.
Not startups.
Not the tech industry.
Tools.
Software was simply the most powerful tool available for building things that didn’t exist yet.
A Strange Moment in History
Over the last few years, something unusual has started happening.
For the first time in my career, I’ve watched software begin writing software.
Artificial intelligence is moving faster than most people realize. Not just faster in capability, but faster in trajectory.
The implications are enormous.
If machines become capable of generating the systems we used to build by hand, the economics of knowledge work will change dramatically.
Entire professions built around expertise may begin to shift.
That doesn’t mean people stop being valuable. It means the landscape changes.
And when landscapes change, the smart move is to step back and ask a bigger question.
Not:
How do I protect the career I built?
But:
What kind of life is resilient in the world that’s coming?
Looking Beyond the Screen
For most of my adult life, my work happened inside a digital world.
Servers.
Code repositories.
Architecture diagrams.
But the longer I worked in technology, the more I noticed something.
The digital world we built was incredibly powerful — but it was also strangely fragile.
Communities became more distributed.
Families more geographically scattered.
Local economies replaced by global platforms.
Convenience went up.
Connection often went down.
At the same time, the most stable and meaningful parts of life remained stubbornly physical.
Land.
Neighbors.
Family.
Real skills.
Real communities.
Those systems don’t run on servers.
They run on people.
Why Commonbound Exists
Commonbound started as a simple question.
What happens when people who built the digital world start thinking seriously about building something more grounded?
My family is beginning a move toward a different kind of life — one that invests more deeply in place, community, and resilience.
This journal documents that journey.
It’s not about rejecting technology. Technology is part of who I am and always will be.
But technology should be a tool that serves life, not the other way around.
Commonbound is where I explore that idea.
The systems we’re building.
The mistakes we make along the way.
And the possibility that the next chapter of the digital age might not be about living more online, but about using technology to build stronger lives offline.
This is the beginning of that story.