ElixirWeekly

E-Mail

can't be blank

Making sure you're human: Name your favorite Elixir kernel module!

(can't be blank)

Subscribe

Every Thursday: No frills, no click-through, no spam.

Here's what the latest issue looks like:

ElixirWeekly by @elixirstatus

Issue #483

This week in Elixir

Ash Framework: Evaluating Ash for Existing Systems
Joseph explores the question how difficult it is to incorporate Ash into an existing codebase.

Listen to Database Changes Through the Postgres WAL
In this in-depth guide to listening to Postgres database changes through the WAL, Peter covers logical replication, publications, replication slots, and an Elixir implementation.

Debugging in Elixir with Observer
Let’s learn how to access Erlang’s Observer GUI and debug an Elixir project that leaks memory:

Announcing ReqLLM 1.0
Mike announces ReqLLM 1.0 - a new, stable Elixir library for working with LLMs.

Even more from around the Elixir community

Thinking Elixir: Searching Across the Hexiverse Podcast

What You May Not Know About `with` - Brian Underwood and Adilet Abylov Video

NxHailo: ML Pipelines on the Edge [nerves Meetup] Video

ReqLLM: The Unified LLM Interface for Elixir Video

Deep Dive into Elixir Logger Blog post

Balancing Auditability and Privacy with Crypto-Shredding Blog post

How I Fell in Love with Erlang Blog post

Curiosum Elixir Survey 2025 Blog post

How To Split Your BIG Ash Resources for Cleaner Code and Faster Compilation Blog post

horde Released v0.10.0 Project update

Submit your blog post/project update

That's it for this round, have a great day!
@rrrene from ElixirWeekly

If you like this newsletter, please tell the world!

You can view this issue in your web browser.

You can subscribe below:

E-Mail

can't be blank

Making sure you're human: Name your favorite Elixir kernel module!

(can't be blank)

Subscribe

Questions & Answers

Yes! Simply post them to ElixirStatus and you can be sure that they land on my radar.

Yes. I'd like to consider myself a trustworthy individual, but then who doesn't?

I am, however, an active member of the open-source Elixir community and the maintainer of Credo and ElixirStatus. I will NOT ruin my reputation by selling your data to a third party.

I just believe that requiring double opt-in to subscribe to any email-based system is a win for both parties: You are safe from unintentionally subscribing and I can be confident that you actually own the email address and want to receive the newsletter I send you :)

Contact

Please contact René Föhring (email or tweet @rrrene for a quick conversation).