What I'm learning while building.

Build notes, lessons learned, and technical essays by Aymeric Dijoux. Not a regular blog — I write when I have something worth sharing.

Based in Paris · Épinay-sur-Orge (Essonne) & Réunion Island

★ Featured

Product engineer, forward deployed engineer: how the developer job is evolving with AI

Product engineer and forward deployed engineer are the two job titles everyone's been talking about since AI started writing much of the code. What each one actually means, why the job is moving this way, and how to make the transition as a developer today.

Nov 3, 2026 · ia · process · indie · 7 min
Sep 21, 2026

Tracing every model call: the rule only holds if a test holds it

"We trace everything" is an intention, not a guarantee: one new code path is enough to open a hole nobody sees. What holds the rule is a test that freezes the inventory of call sites — plus two traps that cost me time.

ia · process · tools · 5 min
Sep 17, 2026

Zero fabrication: when anti-hallucination becomes a product constraint

"The agent hallucinates" is a bad diagnosis: it sends you looking at the model. On an agent extracting data from documents, I watched the guarantee move — from model quality to three engineering constraints. One of them surprised me.

ia · process · build · 5 min
Sep 14, 2026

Your agent isn't re-reading your prompt: the three lifetimes of an agent config

I kept editing the system prompt, kept re-running, and nothing moved. The culprit wasn't a cache: the graph is built once at startup. Three lifetimes coexist inside an agent, and knowing which one applies changes the feedback loop.

ia · process · tools · 5 min
Sep 12, 2026

Image models can't write — so I write the text before they see it

Ask an image model for an App Store screenshot and you get a beautiful visual with an unreadable headline. I inverted the order: a script draws the text, and the model isn't allowed near it. Plus the bit of arithmetic that cost me a full set of screenshots.

ia · tools · mobile · 5 min
Sep 10, 2026

Two branches, two stacks, zero collisions: the bare repo + worktrees workspace

Once you delegate to agents, you always have two or three branches in flight. A plain `git checkout` breaks everything: stash, Docker stack restart, ports fighting each other. Here's the layout that unblocked me — and what it actually costs.

tools · process · stack · 5 min