Product
Clarify the need, the scope and the edge cases before adding features.
A full-stack approach driven by usage.
Jonathan does not pick a technology to tick a box. He first looks for what should become simpler, safer or clearer.
From the idea to real behavior.
I like to start from a situation that resists: files that are hard to organize, secrets scattered everywhere, job offers impossible to follow. Before picking a technology, I try to understand what actually gets in the user's way.
I then turn that understanding into a complete product. I treat the interface, the business rules, the data and the deployment as parts of one system — with particular attention to ambiguous cases, to security, and to recovering from mistakes.
My personal projects are my exploration ground. They let me build beyond an isolated exercise, test my decisions against real usage, and learn to finish properly what I start.
Frontend
Turn rules into understandable, accessible and efficient flows.
Backend
Model data, permissions, errors and transitions explicitly.
Operations
Prepare environments, persistence, logs and deployment as part of the product.
Let's build the next step.
An apprenticeship, a product to move forward, or simply a conversation about a useful application: Jonathan is open to professional exchanges.
See how to get in touch
Contact address still to be filled in.