A software architect who still writes the code.

What I've done

I've been building enterprise software for 30 years. For 18 of them I was the Technology Architect at Old Republic Home Protection, one of the country's largest home warranty companies. Over that time I stewarded a 20-year-old legacy enterprise platform, designed and built its modern replacement (Angular, Spring Boot microservices, SQL Server), and then designed a second greenfield cloud-first system on Azure. That full arc - legacy stewardship, modernization planning, greenfield rebuild - is something most architects never live through even once.

I still write code every day, and I run AI in production, not just in a slide deck. I operate ten live software products, a 59-tool MCP server spanning 12 functional domains, a retrieval-augmented chatbot, and a fleet of autonomous agents that runs my own business operations. That's what keeps my judgment current: when I tell you an AI project is harder than it looks, or that a vendor's cost estimate is optimistic, it's because I've done the work recently myself.

I also spent 18 years explaining technical decisions to non-technical executives and department heads. Getting the business and the technical team to the same understanding is half the job. I can be in a room with your engineers in the morning and your board in the afternoon and give both groups what they need.