About

I’ve spent twenty-seven years in software — first building it, then increasingly leading the teams that build it — most of it on the systems that rarely make it onto a conference slide: large, long-lived, business-critical codebases carrying years of accumulated complexity and often very little documentation. Keeping software like that healthy — and keeping the teams around it productive and confident — is where I learned which changes actually move the needle and which only look like they do.

Most recently I’ve led the engineering team responsible for a sprawling, almost entirely undocumented legacy product, using AI as a deliberate strategic lever rather than a novelty. That has meant recovering institutional knowledge about the product that had been lost, compressing the distance between a reported problem and an actionable diagnosis, and roughly tripling the team’s defect-closure rate — while being just as clear about where AI wouldn’t help as where it would. The hard part is rarely the tooling; it’s the judgment about where to apply it inside a working team without destabilizing what already works.

Llchemy is where I bring that judgment to small and midsize organizations: deciding which AI priorities actually fit a business’s real pain points, where AI isn’t worth the effort, and how to adopt it without betting the business on a trend. My depth is in software and engineering teams — my background runs from bioinformatics pipelines and agency consulting to leading modernization on twenty-year-old platforms — but the strategy question travels well beyond any one field. I’m based in Fort Worth, Texas.