How I approach my work.

Most of the problems I work on already have a history. There are existing systems, business rules, edge cases, and people who know what goes wrong when something changes. I like learning that context before I start building. It helps me make better decisions about the UI, the data, and the integrations behind it.

I'm most interested in software people use every day: internal applications, APIs, workflow automation, and the maintenance work that keeps a system reliable after it ships.

Outside of work, I build side projects, explore AI tools, and keep learning new technologies. I also enjoy home improvement, woodworking, and fitness. Those projects are different from software, but I like the same part of each one: learning how something works and improving it step by step.