The person behind the decisions
Engineer, developer, and product owner
I look at a project through technology, operations, and business because I have been responsible for each of them in my own work.
20+years in software
Over that time, software development has become more than a technical function for me: it is a way to carry a product from intent into operation.
Experience does not make a decision correct by default. It helps reveal material risk earlier, distinguish it from unnecessary complexity, and then prove the choice through an operating result.
How practice changes my decisions
This is not a résumé timeline. It includes only the experience that directly changes how I design a product.
Operating owned systems
Release, monitoring, and recovery are designed before launch, not after the first failure.
Running companies and production
I study the real process, ownership, and human constraints before designing the interface.
Physical engineering
Failure modes, tolerances, and verifiability become part of the design rather than a late addition.
Building businesses and products
Cost, adoption, and ongoing operation are considered alongside technical quality.
AI-assisted work
AI accelerates research and implementation, while verification, architecture, and responsibility remain mine.
Operating products are stronger than a biography
The useful next step is not another list of achievements, but the tasks, decisions, and public verification boundaries of real projects.
View the real projects