ElixirWeekly

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

Here's what the latest issue looks like:

Issue #434

This week in Elixir

Map Lookup in Elixir - a Taxonomy
Matt shows how, by choosing the appropriate lookup method, developers can write more concise and expressive code, improving readability and reducing potential errors.

How I use Erlang Hot Code Updates
Lars explains how the legendary facilities of the Erlang VM are used for mostly pedestrian tasks.

Tower: Universal and Agnostic Elixir Exception Tracker
Gonzalo and team built and open sourced Tower to provide Elixir Exception Tracking with many pre-built reporting options available, including e-mail, Slack, local ErrorTracker and popular 3rd party services.

egze/obanalyze: Real-time Monitoring for Oban
Aleksandr gives us a simple way to monitor your Oban jobs in Phoenix's LiveDashboard.

Even more from around the Elixir community

Thinking Elixir: Thinking Elixir Podcast Podcast

ElixirConf EU 2025: Call for Speakers Conference

Building Beacon #1 - Site Config Blog post

Streaming Remote RSS in Elixir Blog post

Adding Google OAuth to Phoenix Blog post

Advanced IEx Helpers: Mastering Commands and Features in Elixir Blog post

Potions in a Cauldron: Streamline Elixir App Development with Code Generation Blog post

phenixdigital/phoenix_storybook: A Pluggable Storybook for Your Phoenix Components. Project update

Mssantos/ovp: Onde Vai Passar is an Online Schedule Providing Broadcasting Information for Sports. Project update

Assimelha/routes: Type-safe Phoenix Routes in Your JavaScript/TypeScript! 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:

Questions & Answers

Can I submit things I made to be included in the next issue?

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

Is my email address safe with you?

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.

Why do you require me to confirm my email address?

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

Feedback? Questions? Anything else?

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

ElixirWeekly by @elixirstatus

ElixirWeekly

Questions & Answers

Contact