Self-taught. Systems-minded.
Years in live production and AV — where "it works or the show stops" — led to self-taught software work. Same standard, different medium. Based in Denver, working globally.
Background
I came to software from live events — audio, staging, crews, deadlines that don't move. In that world you learn to find the real problem fast, build for the room you're actually in, and own the outcome when something breaks at 7 PM on a show night.
That became the way I build software: web systems, AI-assisted workflows, search infrastructure, automation and public-interest technology. Everything I ship, I also operate — the feedback loop is the product.
How I work with AI
AI speeds up research and drafting. Tests, review and the final decision stay mine. Every automated pipeline I run has human approval steps where it matters — that's what makes automation trustworthy enough to run unattended.
What I won't do
I disclose what I don't know, and I don't manufacture authority I haven't earned: no invented partnerships, no fabricated case studies. My public-interest and homelessness-resource work now lives under Williams Compass, my nonprofit — kept free, and honest about what one person can maintain.
How the work gets done.
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 human.
Search infrastructure
Technical SEO as an engineering discipline — crawling, indexing, structured data, canonicalization.
Automation
Crawlers, scheduled jobs, monitoring, and the human approval steps that make them trustworthy.
Public-interest tech
Free resource platforms for people who need them, built because the gap is often just a bad website.
Full pipeline ownership
Design → build → deploy → operate. One person accountable for the whole system.