I found software by following good advice.

I did not grow up knowing I would work in technology. I found software development in college after a friend suggested it, and it turned out to be one of the better pieces of advice I have taken.

I stayed because I like understanding why a system behaves the way it does, then finding a practical way to make it better. That curiosity also shows up in the software and hardware projects I keep starting at home.

How I lead

Today, I am a partner at Blueprint Software, where I lead technology, build custom software for clients, solve practical business problems, and create internal software for our companies.

I moved into leadership because I wanted to spend more of my time helping other engineers do their best work. In practice, that means making sure people know why the work matters, have the context to make decisions, and get feedback they can use.

I do not want every decision to come through me. My job is to set direction, make the constraints clear, remove obstacles, and step in when a team needs help. The goal is a team that can make good decisions without waiting for permission.

I still care about the technical details. Leadership is better when it stays connected to how software is designed, delivered, operated, and improved.

Beyond work

Outside of work, I spend as much time as I can outdoors with my wife and our dogs. I enjoy hiking, fishing, and hunting, especially when it gets me away from a screen. I also play Dungeons & Dragons, read a lot of science fiction, and listen to more podcasts than I can keep up with.