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

Here's what the latest issue looks like:

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

Run the Timing Task Efficiently in Erlang?
How to complete the timing task quickly and efficiently? Here are three common ways to implement timing tasks and their advantages and disadvantages.

José on Kubernetes and the Erlang VM
José clears up a lot of confusion around Kubernetes and Erlang/Elixir. There's a really good Joe Armstrong quote that paints a good mental picture of the relationship.

Elixir Trickery: Cheating on Structs, And Why It Pays Off
Elixir’s Struct mechanism is extensively used and it’s both simple and powerful. Michal explains why it is sometimes good to cheat on it a bit, especially in library development.

Dynamic Conditionals with Ecto
Walkthru from Dan on how to prototype a complex search with Dynamic Conditionals in Ecto.

The Nostalgic Snake Ladder Game - Part 1
Great post about building a Snake-Ladder game with Elixir.

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