About
I learned to build by needing things that didn't exist yet.
Twenty-five years in live production taught me to fix things under pressure with whatever was on hand. That instinct carried straight into software — self-taught, systems-minded, and still happiest solving a real problem for someone who actually needs it solved.
A different route into technology
From live production into software
I didn't come up through a computer science program or a bootcamp. Live events, corporate AV, broadcast signal chains, and theater operations came first — the kind of work where the show still has to happen at the scheduled time regardless of what broke five minutes earlier.
That environment teaches you to diagnose fast, work with what's actually in front of you, and make changes you can undo if they don't work. Eventually I pointed the same instinct at software, self-taught and mostly by necessity: web systems, technical SEO, automation, and now AI-assisted development. I favor understanding over recipes — knowing why something works, not just how to configure it.
What I build
What I build
Most projects touch more than one of these.
- Web systems
- Sites and application-style systems in PHP or JavaScript — framework or none, depending on what the project needs.
- AI-assisted workflows
- AI speeds up research and drafting. Tests, review, and the final decision stay mine. How I use AI
- Search infrastructure
- Technical SEO as an engineering discipline — crawling, indexing, structured data, canonicalization. Live Event SEO
- Automation
- Crawlers, scheduled jobs, monitoring, and the human approval steps that make them trustworthy to run unattended.
- Public-interest technology
- Free resource platforms for people who need them, built because the gap is often just a bad website. Public-interest work
Process
How I work
- Find the real problem, not the assumed one.
- Build something useful, not something impressive.
- Put it in the real world, not a demo environment.
- See what actually breaks.
- Improve it, then repeat.
Background
Experience that carries over
Live production and AV work builds specific habits that turn out to matter in software too: diagnosing under time pressure, coordinating a crew toward a fixed deadline, and getting comfortable with the fact that something will go wrong in front of an audience regardless of how well you prepared.
Years of venue and promoter workflows also mean I don't need the terminology translated when a client works in live events. And the instinct for staged, reversible changes — the one that keeps a live show from going dark — is the same instinct that keeps a production deploy from taking a client's site down.
What matters to me
What matters to me
Accuracy is a trust problem, not a content problem. On the public-interest sites, a stale listing can send someone to a shelter that's already full — that's treated as a safety issue, not a typo.
I disclose what I don't know, and I don't manufacture authority I haven't earned: no claimed nonprofit status, no invented partnerships, no fabricated case studies.
I work independently and self-fund the public-interest projects on my own time. That keeps them free, and it keeps me honest about what one person can actually maintain.
Selected work
Selected work
- FieldCompass — privacy-first navigation for homeless services in Denver.
- BestModel — casting and model management platform.
- OSINTCompass — a curated directory of public-source research tools.
- EventCrewOS — scheduling and staffing system for event crews.
Let's build