Learning Elixir's syntax is only part of adopting it. Gabriel Ortuño explores four shifts in how teams model data, structure transformations, and handle failures, with examples of habits that can carry over from object-oriented code.
What do we mean by local-first: data ownership, offline use, or speed? Bart Blast discusses the three definitions, why sync engines diverged from the original vision, and what that means for Hologram.
How can AI agents inspect production without full access to your nodes? Juan Azambuja introduces Porthole, which exposes BEAM runtime data through read-only SQL over MCP, with limits on what agents can collect.
Learn recipes and patterns specific to Elixir/OTP and leverage the power of the BEAM. Some examples: cron jobs with GenServer, hydrating ETS from DETS, delegating work with supervision trees, and dynamic rate limiting.
After the eMudhra compromise, Charlie Forêt expected a redeploy to fix his Phoenix app's TLS trust. He shares what he found across the OS and certifi bundles, including a hackney detail that made replacing trusted roots insufficient.
Masatoshi Nishiguchi got Elixir running on a UIAPduino with just 64KB of flash and 8KB of RAM. He shows how he reduced AtomVM, built the firmware, and blinked an LED on real hardware, along with the experiment's current limitations.
What would "let it crash" look like beyond the data center? Brooklyn Zelenka connects BEAM ideas to local-first software, covering CRDTs, capability-based access control, and collaboration that keeps working when devices disconnect.
We're looking for a AI-first Full Stack Engineer with a strong backend and Elixir expertise to own partner APIs and dashboards that power the qiibee ecosystem.
