ElixirWeekly
Every Thursday: No frills, no click-through, no spam.
Here's what the latest issue looks like:
Welcome to Issue #98
Apologies! This issue is a day late due to some GDPR related work.
Talking of GDPR: I added a data privacy policy link to https://elixirweekly.net/ (scroll to the bottom; not sure if this makes sense, since this is a non-commercial hobby I maintain in my free time, but better to be safe than sorry).
If you want to unsubscribe from this newsletter at any time, there is always a link at the bottom of this email!
This week in Elixir
Elixir - Quick Reference for Debugging Techniques
Much has been said about Elixir debugging techniques, but in this post, Leandro gives a quick overview of all possible options to serve as a go-to reference when you need to debug Elixir code.
Rethinking app env
This great article by Saša questions current practices of using application environment and config scripts, and proposes a different approach to configuring Elixir based systems.
Elixir Backend Engineer Wanted at Wooga!
Wooga Backend Engineering team is responsible for providing the tools and services we use to build, scale and operate all our games to excite millions of players around the world every day!
Going Multi-Node with Elixir
Last month ExVenture, a multiplayer text-based game server, went distributed. This is a blog post showing that journey and how simple it ended up being.
On Guarantees of Phoenix Presence
Phoenix Presence is awesome! But it’s important to know about its tradeoffs and limitations before deciding to use it.
Introducing Level, an OSS app Built in Elixir + Elm + GraphQL
Level is an alternative to real-time chat, optimized for deep focus. This is an early-stage project under active development.
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 :)
Contact
Feedback? Questions? Anything else?
Please contact René Föhring (email or tweet @rrrene for a quick conversation).
