The project1 min read
Reading paths
A reading order depending on what you’re looking for, with the time each step takes, then the map of every section.
This doc is long, and nobody needs to read all of it. So I suggest one path per reader. Each path gives an order and says what you’ll find at each step. Once you start one, a bar at the bottom of the screen shows the step you’re on and takes you to the next one.
The time shown is computed from the text of each page. If a step only points to one section, only that section is counted. Pages marked FR haven’t been translated yet.
You are hiring6 steps · about 12 min
The essentials
What the project is, what it shows for a given role, and how I use AI as leverage.
- 2 min
At a glanceCase study: Meubles Morinière
The trade, the two applications, the stack and the guarantees the software checks today.
- 2 min
My roleCase study: Meubles Morinière
What I do at each stage of the project, what the AI does, and my team experience outside this project.
- 2 min
What this project demonstratesCase study: Meubles Morinière
What the project shows for the role you are filling, with the page where you can check it.
- 4 min
What I claim, and what proves itSkills and evidence
The skills I claim, each one next to the code or the test that proves it.
- 1 min
How I build Claude Code into my development, and what I keep in hand: the technical choices, the consistency of the product, the quality delivered. The opening of the page sums it up, and the rest details it with the records.
- 1 min
ContactCase study: Meubles Morinière
To talk about it, or to see the code in an interview.
You lead an engineering team6 steps · about 51 min
The decisions
The choices that shape the software, what they cost, what I refused to build and how I work with coding agents.
- 5 min
DecisionsCase study: Meubles Morinière
The decisions that shape the software, each with what it costs.
- 7 min
Who depends on whom in the repository, what each application owns, and what talks to what once deployed.
- 7 min
Holding a piece during payment
A full study, from the problem to its limits: a one-of-a-kind piece sells in the store while another customer pays for it online.
- 5 min
Décisions d’architecture(in French)
The same choices as ADRs, with what the sources confirm and what remains an assumption.
- 13 min
Dette, risques et évolutions(in French)
What I did not build, the debt I keep and the risks that remain.
- 14 min
What I framed, decided and verified, what the tool produced, and what I take from it.
You write software7 steps · about 1 h 20
In the code
How the repository is organized, what the database guarantees, how pages render, and what judges a change before production.
- 7 min
The map of the repository, the direction of dependencies and what runs once deployed.
- 4 min
The layers of each application and the imports the linter rejects.
- 29 min
The Prisma model, and what Postgres itself rejects when money, stock or the law is involved.
- 19 min
Rendering, caching and state with Next.js and React, and their limits.
- 8 min
What the software protects, against what, and where each guarantee can be checked.
- 7 min
Qualité et livraison(in French)
The route of a change to production, and the check that judges it at each stage.
- 4 min
To go further, the problems where the obvious solution was not enough.
Browse by topic
In the menu, pages are sorted into groups, and each group answers a question. The case study also says which pages to read depending on the role you’re hiring for, from full-stack development to applied AI.
The project
What is it, and who built it?
- Case study: Meubles MorinièreA furniture workshop and store, two applications in production on one shared database, and a project I led on my own. I go through the context, the problem, the constraints, the decisions, the implementation and the results, and every claim links to its evidence.
- Skills and evidenceThe skills I claim in full-stack development, architecture, security, UX and quality. Each one has its evidence, read from the repository at build time: code, a test, a diagram or a decision.
- My contribution and AIAI as leverage, engineering as the standard. How I design and build with Claude Code, what I frame, decide and verify, and the records that show it.
The product
What does the software do?
- ERP(in French)L’outil de l’équipe, ce qu’il couvre, comment un module est rangé, et ce qui tourne même quand personne ne l’ouvre.
- Fisher, l’assistant IA(in French)L’assistant de l’ERP, ce qu’il fait, et les garanties que le code lui impose.
- Site public(in French)Comment le site est construit, du catalogue au paiement, les règles qu’il suit et la carte de son code.
- Logique métier(in French)Où sont les règles du magasin, comment on compte l’argent, et pourquoi chaque règle n’est écrite qu’une fois.
The code
How is it built?
- Architecture(in French)Le monorepo, ses applications Next.js et ses paquets : ce qui appartient à chacun, qui dépend de qui, qui parle à qui en prod, et où tout est hébergé.
- Sécurité(in French)Ce que le logiciel protège, contre quoi, et où chaque garantie se vérifie, pour les comptes, la base, les prestataires et les échanges entre les applications.
- Qualité et livraison(in French)Le trajet d’un changement de mon poste jusqu’à la prod, le contrôle qui le vérifie à chaque étape, le risque que chacun couvre, et ce qui n’est pas couvert.
Engineering choices
Why is it built this way?
- Technical case studiesEleven engineering problems that came up on the project, from a one-of-a-kind piece sold on two channels to an assistant that must not make up a single figure. For each one, I give the solution that was kept, what it achieved and its limits.
- Décisions d’architecture(in French)Les décisions qui donnent sa forme au logiciel, au format ADR. Je sépare ce que les sources confirment de ce qui reste une hypothèse.
- Dette, risques et évolutions(in French)Ce qu’on n’a pas construit et pourquoi, la dette qu’on garde en connaissance de cause, les risques qui restent malgré les gardes, et le signal qui ferait changer d’avis.