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
Ti Boug, my iPhone app against the cost of living in Réunion: the real daily prices of fruit & veg, their season, and an AI-composed basket — from the official DAAF price bulletins. What it does, the stack, and where the build stands.
"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.
"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.
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.
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.
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.