The work behind the site.

I ran IT at 23 for a growing software company. The job description was vague; the reality was everything from server racks to database design to the tools the sales team needed. That is where I learned that technology leadership is mostly about decisions, and that the hardest ones are usually not the technical ones.

The pattern has stayed the same. The roles got bigger, the systems got more complex, and the technology changed several times over. The question stayed: what does this system actually need to do for the business, and what is the most durable path to get there?

Most of my career has been in life insurance and regulated financial services. Those environments reward patience and clear thinking. You cannot move fast and break things when the things you might break are customer policies, regulatory relationships, or payment systems that have to work every morning. That constraint is not a limitation. It is a useful design pressure. I learned to build systems that are easier to change over time because I had to.

I am interested in AI in the same way I have been interested in every technology shift: not for what it can do in a demo, but for what it actually changes in production, in workflows, and in how teams make decisions. The governance model matters as much as the model selection. I have spent the last several years working through that translation problem at enterprise scale.

Outside the enterprise work, I build things. The Career Schema that powers this site started as a frustration with resume formats. The brewing analytics work started because I wanted better data on my fermentation outcomes. Both turned into systems problems, which is usually where I end up.

The site exists to make the thinking visible. If something here connects with a decision you are working through, a direction you are setting, or something you want to build, reach out.