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

Here's what the latest issue looks like:

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

Code Elixir LDN is a one-day conference bringing together the Elixir community to share, learn and inspire.

Phoenix Live View Debounce
While waiting for phoenix live view debounce feature, it is easy to add it with very few lines of code.

From Webpack to Parcel with Phoenix
You may have thought about swapping Webpack for another asset bundler such as Parcel. Here's how to do it in 5 minutes.

Using Protocols in Your own Code
Protocols can be a useful tool when building Elixir libraries and provide a way for users to extend your library for their own uses.

Event Sourcing With Elixir - Part 5
In Part 5 of this series on Event Sourcing, Bruno rounds up account closure, deposits and withdrawals to set the stage for transfers using process managers.

ExUnit Deep Dive
Daniel wrote this piece on ExUnit and how it works internally: how the testing framework uses macros and process spawning to run your tests blazingly fast!

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).