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 #503

This week in Elixir

Building a Blog with Elixir and Phoenix | jola.dev
Johanna wrote this about setting up a website using Elixir and Phoenix, leaning on NimblePublisher for the blog posts.

BEAM Metrics in ClickHouse
How Andrea & team are periodically dumping metrics about our most demanding BEAM processes into an easy-to-query ClickHouse table.

Software Development in 2026
Aleksei about the five stages of LLM grief, why the models are glorified T9, why context matters more than the model, and the surprising effectiveness of saying ‘please.’

Even more from around the Elixir community

Thinking Elixir: OpenAI Chose Elixir and A VM Inside a VMV Podcast

LiveDebugger 0.7.0 - Node Inspector, Better Global Callback Traces, Nested LiveViews Support Video

ElixirConf EU 2026 on 23-24 April, Málaga & Virtual Conference

Code BEAM Lite Stockholm 2026 Conference

A Devcontainer for Elixir Blog post

Programming Patterns in Simple Words Blog post

How to Build Platforms That Do Not Let Audiences Down Blog post

Build Your Own Elixir Phoenix + LiveView: Step 3: Router DSL (macros) Blog post

Phoenix Scopes vs Authorization: What Developers Need to Know Blog post

Notification-Oriented Paradigm (pon) in Elixir: why the BEAM Fits Reactive Rules Blog post

akoutmos/octo_fetch released v0.5.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).