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

Here's what the latest issue looks like:

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

Testing a Phoenix Application for Credential Stuffing with Elixir, Floki, and HTTPoison
Are you familiar with credential stuffing attacks? Michael shows us how credential stuffing works by writing our own testing program in Elixir.

[video] Elixir's new "dbg" with Pipes
Coming soon: A new Elixir macro that let's you "inspect" your code in a way that's much more tailored towards debugging than the usual interlaced "IO.inspect/2".

Writing Predictable Elixir Code with Reducers
Let’s see how code predictability plays a crucial role in a project’s short and long-term health. We will use Elixir’s built-in features for this, like the pipe operator, tuples, and with blocks.

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