About
I wrote my first code on a Commodore 64 as a kid and started building for the Internet professionally in 1997.
Since then I've started companies, worked across industries, built remote teams, served as a CTO, advised founders, and kept writing code whenever the work needed it. The tools keep changing. I keep changing with them.
80s
I was nine when I got a Commodore 64 for Christmas. I wasted no time exploring what it could do, which mostly meant typing in programs, changing them, and seeing what happened.
One of the first things I remember programming was a tiny green, pixelated hot-air balloon that I could make rise and fall on the screen. It was simple, but I could type something and watch the machine respond.
That was enough. I was hooked.
1997
By the late 1990s, I was working at a TV station in Lincoln, Nebraska, doing a mix of ad programming, graphic design, voice-over work, and whatever else needed doing.
At the same time, I was building websites on the side. I also met my future wife, Jennifer, a talented writer, and we bonded over a shared love of travel.
In 1997, building for the Internet became professional work for me. The web was obviously going somewhere. I wanted to go with it.
00s
In the early 2000s, I started a web development business and later freelanced as a developer, designer, and technical project manager for other companies.
After the dot-com crash and 9/11, the work took me through agriculture, real estate, electrical and plumbing, sales, publishing, and several other kinds of business.
That range turned out to be useful. Software makes a lot more sense when you understand the customers, constraints, and business around it.
2008
I bought an abandoned school in Nebraska and turned it into the headquarters for my development company.
From there I built a remote web development business, which gave me the freedom to spend about half the year traveling through places including India, China, Morocco, and Mexico while working with clients and distributed teams.
This was well before remote work became normal. It changed how I thought about clear communication, trust, and what actually matters when people work together.
2015
In 2015, I stepped into my first CTO role, leading a remote Swedish development company.
Through the 2020s, I worked as a fractional and remote CTO for SaaS startups and scale-ups around the world. That included taking a marketing-attribution platform from a spreadsheet concept to a system processing millions of data points each day, then building and leading its senior engineering team.
I now divide my time between Texas and Mexico, working with clients across the United States and Europe. The title matters less to me than owning the technical problem.
Now
Today I run my entire practice AI-native. Multi-agent systems help plan, write, review, and ship the software behind a portfolio of products I build and operate, including seeProgress.ai, my team-activity intelligence product.
It is the biggest change in how I work since the Internet itself. I'm not interested in protecting old workflows just because I spent decades learning them. Code can be produced differently now. Good technical judgment still matters.
That practice shapes how I advise, review, and build with founders today.
You don't need to know whether you need a CTO, a code review, architecture help, or just another experienced set of eyes. Tell me what you're building, what you're worried about, or where you're stuck.
A paragraph is great. “Can you call me?” works too.
