About
A few projects, done well .
Intro
I'm a software developer with a polyglot approach. I work across stacks because I believe the problem should drive the tech choice, not the other way around.
I take on a few projects at a time. A client deserves real attention, not the last slice of my time after ten others.
What interests me: technical problems where the solution isn't obvious. Serious companies that want to build something that lasts.
How I work
Four phases, always the same.
- 01
Analysis.
I understand the problem before proposing the solution. A call or two, some uncomfortable questions, a written technical proposal.
- 02
Proposal.
Architecture, stack, timeline, cost. All on paper, no surprises mid-project.
- 03
Iterative development.
Real, scheduled deliveries. You watch the product grow, give feedback, we adjust course early if needed.
- 04
Delivery and training.
Documentation, handover, training session for the team. What I build stays yours.