Blog
realtime
Persistent connections, presence, and the parts of an interface that only work while the server is still on the line.
-
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.
-
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.