I want to do work people can pick up and carry forward.

That might be a client system the team can change, an open-source tool someone else can build on, or an article that helps someone make a decision.

I work best with people who can use the result, tell me when it is wrong, and carry it forward. Their response is part of how I judge the work.

Client work has deadlines, old software, complicated rules, and people who need the result. I keep some projects open source because I enjoy building them and can share them. I write down what the tools change and where they fail.

I spent more than fifteen years building web applications, coaching developers, and leading engineering teams. Then I focused on data and led data organizations at JPMC, Zapier, and Shopify. Recent client systems have been in health research and financial services.

A demo can look good while the real work gets worse. I want to know how the work holds up under pressure, who checks the result, and who can change the system when it is wrong.

After NerdWallet, I expected another engineering or data leadership role. I started building with coding agents every day and found I wanted to stay close to the work. I now choose projects with people who will use what we build, tell me when it is wrong, and take it further themselves.

Earlier work

My résumé and LinkedIn cover the earlier roles. The current work is the better description of what I do now.

Room to choose

I limit consulting so I have time for my family, open-source work, writing, and things I want to make—like a physical knob on the couch controlling the system in the basement.

See the work, read the writing, or tell me what you are working on.