When AI agents fail…. 😂😂😂

“The business doesn’t want alarms. It wants reactive plans.”

@aramallo’s team built a scheduling solver in Bondy in a week. It once took him three months with an operations research expert. youtu.be/Id-K5UrI1BQ

Anyone in Innsbruck today or tomorrow? Heading up for Inday Students, giving a talk on how OTP and coding agents are a match which has evolved over time: uibk.ac.at/en/informatik/…

It was great recording a @BeamThereDT episode on Jido where @allenwyma and I speak to @mikehostetler. We looked at Jido & talked about the migration & separation of concerns which lead to the v2.0 rewrite. Released tomorrow, this is one not to be missed. beamtheredonethat.com

I started Barrel a few years ago as an alternative to CouchDB. Put it aside for a while, then came back to it with a broader direction.

A database for AI agents, with documents, files and vectors managed together.

Built in Erlang, open source.

barrel-db.eu

Sam Aaron turned the whole Code BEAM Europe audience into a live coded phone orchestra, playing synths on every phone with SuperSonic and Phoenix PubSub. ElixirConf EU 2027 Call for Talks is open until 15 December: sessionize.com/elixirconf-eu-… Watch: youtu.be/1zqeXkS3gAE

Recording with two of my favourite people! Great having @OmerK and @fhunleth on the @BeamThereDT podcast, sharing knowledge and insights on the boundries between hardware and software. Coming soon at a podcast distribution platform near you: beamtheredonethat.com

The Call for Talks for ElixirConf EU 2027 is open!

After Code BEAM Europe 2026, the next stop for the community is Lisbon, 22-23 April 2027. Got something to share about Elixir or the BEAM? Submit by 15 December: sessionize.com/elixirconf-eu-…

#ElixirConf #Elixir #BEAM

“An agent is an actor. It has durable state, an address you can send messages to, and it can say no.”

@aramallo on agents that are more than an LLM in a loop, and why the BEAM suits them. youtu.be/Id-K5UrI1BQ

“Saying coding is solved is completely wrong. For everything else, 50% of what it generates is garbage.”

@aramallo on where coding agents helped build Bondy, and where they kept breaking the architecture. youtu.be/Id-K5UrI1BQ

erlang-rocksdb 3.2.0 is out.

RocksDB 11.13.2, two-phase SST ingestion, per column family compaction abort, new tuning options, and many NIF safety fixes: shared handles, close/1 now waits until the DB is closed.

github.com/EnkiMultimedia…

ElixirConf EU 2027 Call for Talks closes 15 December! Do you know Elixir or the BEAM and have something to share? Speakers get a free ticket, speakers' dinner, a confirmation letter and a promo code to share. sessionize.com/elixirconf-eu-… #ElixirConfEU

“You end up describing the same thing three times, and the three descriptions drift apart over time.”

@aramallo on why Bondy had to be a language and not a library. youtu.be/Id-K5UrI1BQ

A look back at MQ Summit 2026 with our host Simone Jain. Featuring insights from Richard Coppen, John Samuel, Ali Alemi, and Clemens Vasters on the future of messaging systems. Thank you to everyone who joined us in Haarlem and online. See you in 2027!

#MQSummit2026 #Messaging

"It really is just an amazing place to be." On the floor at Code BEAM Europe 2026, @samaaron captures what brings developers together: deep conversations around Erlang, Elixir, Gleam, and concurrent systems.

Thanks to everyone who joined us in Haarlem. See you next year!
6 #CodeSync #BEAM

Rules that took ~800 lines of Erlang: 40–50 lines in Bondy. Alejandro Ramallo on the new declarative, statically typed BEAM language built on Datalog and CHR. youtu.be/Id-K5UrI1BQ

Forward thinkers only: Hacía tiempo no escuchaba un podcast con este nivel de complejidad y potencial. Bondy dot io es un "Backpressure" Programming Language + Plataforma Agéntica Distribuida (la definición psicodélica es mía), lo básico es que es un lenguaje de programación tipaje estático, funcional, relacional y basado en reglas que compila a la BEAM (máquina virtual inicialmente para Erlang que está en desarrollo desde los ochentas).

En este punto si crees que Java/Typescript es el mejor lenguaje del mundo mundial ya puedes dejar de leer, o si crees que todo tiene que ser Rust porque es rápido y es el nuevo amor del tipo que hablan duro. Next.

Lo fumado es que el lenguaje emerge del mundo iot, para poder expresar y operar operaciones distribuidas sobre dispositivos de forma más ergonómica y confiable. Por eso integra elementos funcionales y un sistema de reglas basado en una vaina que se llaman Constraint Handling Rules (CHR) guiño guiño a Prolog (de hecho descubrí que hay cincuenta y pico de lenguajes que aprovechan la BEAM, entre ellos varias implentaciones de PROLOG).

Los 10 primeros minutos son una patada en el culo porque el nivel de abstracción con el que empieza la conversación es demasiado alto, pero luego pasan a un ejemplo de monitoreo remoto de camiones refrigerados que está puyuo.

En este punto uno no puede dejar de pensar en Agentes, de hecho el lenguaje está diseñado con Agentes como first class citizens en múltiples dimensiones. Y efectivamente empiezan a explicar cómo mapear agentes distribuidos y siguen alternando con los camiones refrigerados.

BOOM!

El futuro está lleno de posibilidades y el matrimonio que arreglaron tus padres para ti con un lenguaje de programación te está dejando en el pasado. Besitos.

Vean el video y dense un buen revolcón en las neuronas. Aguanten los 10 primeros minutos que luego todo aterriza.

New @BeamThereDT episode: @aramallo on Bondy, a new declarative BEAM language built on Datalog and Constraint Handling Rules. Shapes that are both type and validator, rules that fire themselves, and gen_reactor, a new OTP behaviour. youtu.be/Id-K5UrI1BQ #Erlang #Elixir

Elixir devs who haven't tried Hologram yet, what's stopped you?

Building a framework is two jobs, the framework and getting people to use it. I'm on the second one now, so here I am asking. Vote below, or reply, blunt is welcome. DMs open too, and reposts help a lot.

Hernán Rivas Acosta’s first Erlang game server held 50,000 players on one machine. The BEAM never hit its limit. The OS did, and the team chose not to raise it. Java would have managed a few thousand. youtu.be/XubYVNbehYc