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

Here's what the latest issue looks like:

Logo ElixirWeekly by @elixirstatus Issue #200
Welcome to Issue #200

Wow, 200 issues! This is the most exiting thing since ... well ... 100 issues!

In earnest: I've been involved in the Elixir community for the better part of a decade now and after all these years the joy of discovering new things in this space has not faded. On the contrary: I think the curiousity, guidance and amazing experiments that are shared in our community have helped me through times when other parts of my life were not in sunshine-mode.

Thank you for taking an interest in the Elixir ecosystem, for reading this newsletter and for being part of the Elixir community.


This week in Elixir

Developing with Elixir/OTP Course Review
Antonio wrote a detailed review of Developing with Elixir/OTP by The Pragmatic Studio.

Local Metrics Aggregation With Counters
Devon needed to get a better picture of how his application’s database connection pool was doing, but there was a bit of a hitch ...

How to Protect Amazon S3 Media Links with Elixir and Arc
In their latest blog post, the fine folks from Coletiv show us how to protect your AWS S3 files in Elixir using Arc.

Elixir Editing on KDE’s Kate Editor
Victor discovered how wrong he was, thinking of Kate as KDE's Notepad, when setup an Elixir development environment on KDE's editor.

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