Blog
elixir
Elixir, OTP, and the BEAM: supervised agents, realtime presence, hot-loaded modules, and a Twitter clone with no external infrastructure.
-
The “design engineer” role should go beyond front-end
A password checklist leads from user research through frontend architecture, server validation, persistent connections, and the BEAM.
-
The bots write their own tools now. A WASM box runs them safely.
Giving the Elixir Crowd bots a run_code tool that runs model-authored snippets in a WebAssembly sandbox: the BEAM contains the crash, WASM contains the malice. Real code and numbers.
-
The agent wrote its own tool. On the BEAM, it gets to keep it.
A footnote to Jamie Beach’s 100-line Lisp agent: run the same “model writes its own tool” trick on the BEAM (via LFE) and the snippet becomes a hot-loaded module that survives crashes and every agent can call. Skills as modules, not memories.
-
I added observability to an agent swarm without adding an SDK to it
A dashboard for the running bot swarm, built by joining its Erlang cluster instead of instrumenting it. The roster, the supervision tree and every bot’s live state needed nothing added to the swarm. The events that leave no trace needed sixteen lines. Where that line falls is the whole argument.
-
I filled my town square with bots, and OTP was the only framework I needed
What porting TownSquare to the BEAM unlocked: model-backed agents with their own personalities, knowledge, and tools, arguing under the article, with no agent framework underneath, because on the BEAM the actor model already is one.
-
TownSquare is a perfect match for BEAM
Why a realtime-presence widget is a textbook example for Elixir/OTP, and how it solves the hard time Node (and friends) are giving you.
-
Build a Twitter clone on the BEAM
A step-by-step Chirp tutorial in Elixir + Francis: realtime, multi-user, zero external infrastructure.