Hi, I'm André
I'm a solo developer building systems in Rust. Most of my time goes into AgenticOS, a personal agent-infrastructure platform: persistent multi-layer memory for coding agents, MCP servers, hook-based lifecycle automation, and multi-agent orchestration. The rest is split between web work, analytics pipelines, and 3D/VFX tooling (Houdini, Blender).
Here I write about building and measuring agent systems - what actually works, what silently breaks, and how to tell the difference.
Recent posts
-
Letting an agent write to my production CMS
Handing an agent write access to a live CMS is not a drafting problem, it is a blast-radius problem. The work that made it safe happened before the agent existed: collapsing eighteen write paths into one seam that a test can enforce.
-
Testing a data pipeline against the spreadsheets it replaced
Replacing a reporting workbook means first proving you match it. Then the diffs start pointing the other way, and you find out the report you were treating as the specification does not reconcile against the warehouse it came from.
-
Audition the voice before you commission the work
A persona config for AI-generated writing is write-only: you describe a tone in prose and find out whether it worked after paying for the full piece. The fix is a preview agent so cheap and so constrained that sampling the voice becomes free.
-
Giving my agent a map of the codebase (drawn partly from its own footsteps)
Every agent session used to start with grep archaeology: rebuilding a mental model of the repo from scratch. Now each project carries a code map fusing static structure, git history, and a signal most tools ignore - which files the agent itself touched together in real sessions.
-
Documentation my agents can trust (and why it made me faster too)
My technical posts get written in an afternoon, weeks after the work, without reconstructing anything. That is not memory. It is a documentation standard designed for agents: immutable decisions, plans with stable task ids, and one authoritative home per question.