
Mountains
Distance helps me see systems more clearly. A few hours away from the screen often turns a tangled problem into a simple path.
Founders mindset
Behind every system I build is one question:
What problem are we really solving?

I didn't start with coding.
I started with people.
As a fitness coach and creator of the Fitcrates brand, I learned how to ask questions, understand motivations and help people achieve meaningful goals.
Later I moved into management and discovered another side of business: priorities, budgets and decision-making.
Software became a natural extension of that journey.
Today I use technology to solve business problems with the same mindset that guided me from the beginning: understand first, build second.
How I think
I start by naming the real problem, not by picking a stack. The useful answer is often simpler than the first idea.
Good systems feel calm. I remove needless moving parts so teams can understand, change, and trust the product.
The point is not code volume. The point is a clearer process, a faster decision, or a user experience that finally clicks.
Small gains compound. Software, racing, training, and business all reward careful feedback loops.
Thought stream
Question
Understand the business, the user, the constraint, and the uncomfortable part nobody has named yet.
Simplify
Turn messy needs into a small set of decisions: data, flows, interfaces, risks, and tradeoffs.
Create
Ship the core experience with performance, maintainability, and a visual system that supports the idea.
Iterate
Remove friction, test the assumptions, and polish the parts users actually touch.
Prepare
Leave the system ready for growth: fewer surprises, cleaner content paths, and room for future work.
Me privately

Distance helps me see systems more clearly. A few hours away from the screen often turns a tangled problem into a simple path.

Psychology, physics, maps, patterns, and old questions. I like understanding how things work before I try to improve them.

Simracing trained the same instinct I use in product work: observe precisely, adjust deliberately, repeat until it feels inevitable.
Understand first.
Build second.
Create something that solves a real problem.