What this site is

I run a three-location tennis operation in Austin. About 50 staff, open 363 days a year, thousands of players coming through the courts. A job like that produces problems at a steady rate: a certification lapses quietly, an inventory count drifts, a payroll recalculation eats an afternoon. I have an engineering degree, so at some point I stopped tolerating the recurring ones and started fixing them with software.

This site is where I post that work. Expect short writeups on the tools I build, the migrations I run, and the operational decisions behind them. Some notes will be text, some video. None of it is polished thought leadership. It is a working log.

If any of it is useful to you, or you are automating something in your own business and want to compare notes, email me.