I automated my job search across 7 job boards

A single API key meant a routine upstream 5xx put the whole provider into a 60-second local blackout inside my own gateway, and for months I read the retries that always failed inside that window as proof the vendor itself was unreliable.

I built persistent memory so AI agents would stop forgetting what we were doing. Then I noticed it was keeping me oriented too, and that I was already living inside a crude version of a neuroscience experiment I was running on a fruit fly.

external memory survives a substrate reset while plasticity does not

I’m awake typing this at 5 AM on a Sunday morning, plagued by two issues: the modern operating model...

In the previous post, we taught a model to read our documents. It could search a pile of files and...

Go has two levels of visibility, and the lower one covers the whole package. A convention fills the gap, and it lives only in the heads of the people who wrote the package. An AI agent does not read heads.

When an agent builds something worth keeping, the instinct is to save the whole environment. That is the wrong thing to keep. A Workshop stores the intent (a re-derivable recipe) instead of a frozen filesystem full of debris and secrets.

In March 2025 I built mcp-profiler-bundle, a Symfony bundle that let AI coding agents read the...

🏃 TL;DR In the previous article I built a semantic product search on top of Amazon...

Eight thousand developers starred a self-hosted agent this week. Most will run it on a box nobody watches at night. Three scripts decide how that ends