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

Here's what the latest issue looks like:

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

Spawnfest 2018 is Less than a Month Away! Get Your Team Ready!
Spawnfest is an annual 48-hour free online development competition for the BEAM community around the world where you have exactly one weekend to create the best applications you can.

The Dangers of GenServers
Overusing GenServers is a common mistake when getting started with Elixir. This blog post goes over the pitfalls of using GenServers and potential strategies to avoid them

A Simple, Drop-in Plug for Shallow ETags
Ever wondered why there was no ETag plug? Well, now there is! Start using it now and reduce the bandwidth of your Phoenix application!

Kubernetes-native Phoenix Apps: Introduction and Part 1
This is a new series about running Elixir Phoenix apps on Kubernetes, describing an opinionated and focused approach.

ActiveRecord Smell With Elixir/Ecto
A quick how-to on bringing some ActiveRecord goodness into Elixir/Ecto.

Don't Repeat Your Domain Knowledge
Chen often feels that we are not using modules/functions to extract domain knowledge.

Updating Hex.pm to Ecto 3.0
Ecto 3.0 is just around the corner and as you may already know, it has reached a stable API. To make sure everything works properly, Wojtek thought: "Lets try updating one of the first projects that ever used Ecto: Hex.pm".

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