The through-line in my work is not a job title. It is a test: can the next person run this without calling the person who built it? Everything below is the same answer in different materials.
Operating background
Seven years directing capital projects at Rocky Mount, a 50-acre state historic site in East Tennessee and a National Historic Landmark administered by the Tennessee Historical Commission. Scope, schedule, budget, contracts, compliance, and coordination across fifteen-plus stakeholder groups under U.S. Department of the Interior preservation standards. Projects from $5K HVAC retrofits to $350K full-scope restorations.
Industrial foundation
Early career in industrial controls at Occidental Petroleum's Elk Hills field. Built .NET dashboards for the non-control gas plant SCADA system in active 24/7 production. Hands-on with SCADA, PLC, and RTU systems in a regulated operating environment. That is where the preference for boring, inspectable systems started.
Strategy and teaching
Baldrige examiner with the Tennessee Center for Performance Excellence. Marketing faculty at King University. MBA in marketing. The classroom and the historic site feed the same discipline: how institutions make their value visible to the people they serve.
Why software
I build production software in TypeScript, React, and Python because the work needs tools that survive contact with reality. Internal systems, public platforms, and operating software, built from operational need rather than software for its own sake.
Working principle
Clever breaks. Boring lasts. The clever version impresses in the demo and strands you when the person who built it moves on. The boring version is still running, and still legible, long after. That is the version I build.