What started as a fascination with computers grew into a career in systems, networks, security, and infrastructure. Along the way, I've built websites, restored classic boats, solved technical puzzles, and learned new things simply because I enjoy figuring out how things work.
Today, artificial intelligence feels like the next chapter. Rather than chasing technology for its own sake, I'm interested in what it can help people create, preserve, and share. That curiosity led me to build my own private AI environment and, eventually, to begin developing Life History.
I've always been someone who wants to know how things work — and usually can't resist trying to make them work a little better.
Sometimes that means building networks and servers. Sometimes it means restoring a 1978 Glastron, working on a classic wooden boat, rebuilding a website I first created in the 1990s, or experimenting with artificial intelligence in my home lab.
The technology has changed enormously over the years. The curiosity really hasn't.
Technology has been a big part of my life, but it isn't the whole story.
I've always been someone who wants to know how things work — and usually can't resist trying to make them work a little better. Sometimes that means building networks and servers. Sometimes it means restoring a classic boat, working around the house, taking photographs, or building something simply because I want to know whether I can.
Family has always mattered more than the machines. As I've gotten older, I've become increasingly interested in preserving the stories, photographs, and experiences that connect one generation to the next. That interest eventually became Life History — a project using AI to help capture personal and family history before those stories disappear.
I'm approaching a different chapter now: more time for family, boats, old stories, new projects — and perhaps the occasional Tuesday when absolutely nothing needs fixing.
I'm certainly not finished building things. I'm just getting more selective about what I want to build and why.
And like any properly managed technology operation, mine remains subject to unscheduled interruptions from Rocky, who maintains very strict service-level requirements concerning dinner.
Thirty years on the web and even longer around computers, I'm still learning, experimenting and wondering what I can build next.
Some projects solve practical problems. Some preserve pieces of the past. Others exist simply because something made me wonder, “Can I make that work?”
That's what Webweaver is today — a place to share some of what I've built, what I've learned, and whatever comes next.