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

Here's what the latest issue looks like:

Logo ElixirWeekly by @elixirstatus Issue #278
This week in Elixir

Pitfalls of Metaprogramming in Elixir
In the final part of this series on metaprogramming, Jia looks at three common pitfalls you might encounter when using macros in Elixir.

Credo 1.6 released
Credo 1.6 has finally been released. Check out First-Run Mode and Pinning your Checks in Credo's Config.

Exception Monitoring for Elixir Phoenix with Sentry
Jack wrote this guide to show you how to set up exception and error monitoring for your Elixir Phoenix application with Sentry to get notified when users find an error in your app.

Even more from around the Elixir community

TIL: Phoenix Live View Enable Profiling Misc

Thinking Elixir: Elixir at Supabase with Paul Copplestone Podcast

Elixir Wizards: Re-Platforming One of the Original Dot Coms in Elixir with Angel Jose Podcast

Using Rust with Elixir for Code Reuse and Performance by Niklas Begley Video

100 Years of Erlang | Quinn Wilton | Code BEAM America 2021 Video

Pattern Matching Trouble in ExUnit Blog post

Ecto: An Introduction to Elixir's Database Toolkit Blog post

Exception Monitoring for Elixir Phoenix with AppSignal Blog post

Integrating AppSignal with Phoenix Liveview Tutorial Blog post

Phoenix Liveview - From --no-html to Html & Liveview Blog post

christian-fei/crypto_watch Project update

pawurb/ecto_psql_extras: Ecto PostgreSQL Database Performance Insights 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 :)


Feedback? Questions? Anything else?

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