Skip to Content
Meubles Morinière

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.

  1. At a glanceCase study: Meubles Morinière

    The trade, the two applications, the stack and the guarantees the software checks today.

    2 min
  2. 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
  3. 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.

    2 min
  4. 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.

    4 min
  5. My contribution and AI

    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
  6. ContactCase study: Meubles Morinière

    To talk about it, or to see the code in an interview.

    1 min
Start this path

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.

  1. DecisionsCase study: Meubles Morinière

    The decisions that shape the software, each with what it costs.

    5 min
  2. Architecture(in French)

    Who depends on whom in the repository, what each application owns, and what talks to what once deployed.

    7 min
  3. 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.

    7 min
  4. Décisions d’architecture(in French)

    The same choices as ADRs, with what the sources confirm and what remains an assumption.

    5 min
  5. Dette, risques et évolutions(in French)

    What I did not build, the debt I keep and the risks that remain.

    13 min
  6. My contribution and AI

    What I framed, decided and verified, what the tool produced, and what I take from it.

    14 min
Start this path

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.

  1. Architecture(in French)

    The map of the repository, the direction of dependencies and what runs once deployed.

    7 min
  2. Rangement du code(in French)

    The layers of each application and the imports the linter rejects.

    4 min
  3. Données(in French)

    The Prisma model, and what Postgres itself rejects when money, stock or the law is involved.

    29 min
  4. Next.js et React(in French)

    Rendering, caching and state with Next.js and React, and their limits.

    19 min
  5. Sécurité(in French)

    What the software protects, against what, and where each guarantee can be checked.

    8 min
  6. Qualité et livraison(in French)

    The route of a change to production, and the check that judges it at each stage.

    7 min
  7. Technical case studies

    To go further, the problems where the obvious solution was not enough.

    4 min
Start this path

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?

The product

What does the software do?

The code

How is it built?

Engineering choices

Why is it built this way?

On this page