About

I’m an engineering leader based in Richmond, Virginia with 17 years in software. I’ve been a Scrum Master since 2014, back when that meant arguing about story points rather than about agents.

I came up through engineering rather than around it: engineer first, then manager, now a servant leader. The domains have moved around a fair bit, from cloud communications and digital identity, to a consumer marketplace used by millions of people, to regulated finance. What carried across was smaller than any of that. How you get a team to tell you the truth early. How you keep delivery honest once the schedule starts arguing back.

The visible half of the job is design, development and delivery of web applications. The half that decides whether any of it lands is trust, feedback, and a team willing to say out loud when something is wrong. I do more listening than the title suggests.

Most of what I think about now is what AI changes for a team rather than for one person. The single-developer version of that story is well covered by this point: somebody writes code faster. The team version is messier. What happens to code review, to onboarding, to the question of who actually understands the system, once most of the typing isn’t being done by people?

I don’t think you can answer that from the outside, so I build things. Everything on the home page is something I actually run and have kept running. They’re deliberately small. A nightly pipeline that costs almost nothing and has never needed a server has taught me more about where the leverage sits than any large system I’ve worked on.

There’s a pattern across all of it: everything is files. No database, no CMS, no dashboard quietly holding a setting nobody can review. If a rule matters, something in the build fails when it gets broken. That’s slower to get going, and it’s most of the reason these things are still running.

Elsewhere

• LinkedIn
• GitHub
• Daily Kickoff, most days