Three architecture decisions that saved my projects
Four real production decisions: three paid off, one cost six weeks. The useful part is the trade-off, not a generic best practice.
English summary
This article walks through architecture decisions made under real product pressure: removing REST endpoints, extracting reusable patterns, accepting or refusing complexity, and paying the cost when the wrong abstraction wins.
Key takeaways
Senior architecture is mostly deciding what not to build.
A decision is only good in relation to the product constraint it serves.
A bad abstraction can cost more than a bad implementation.
Original long-form article
The long technical article is available in French with code, context and detailed examples. The English page gives the recruiter-readable summary and the main engineering points.
Open the French articleNext step
Sounds like something you need shipped? Let's talk.
I take on critical technical work — from scoping to production, no debt or lock-in once it's handed over. Fastest way to see if it fits: a 30-minute call.
I reply within 24h — often sooner.