ElixirWeekly
Every Thursday: No frills, no click-through, no spam.
Here's what the latest issue looks like:
This week in Elixir
Developing for Alexa using Elixir
The folks at LessEverything wrote an Alexa Skill in Elixir for their own personal use. Here's what they learned in the process.
How Pattern Matching works in Elixir
Pattern Matching is one of the fundamental concepts that we need to master while learning Elixir.
Introducing Weave for Elixir
Weave provides runtime configuration. This becomes relevant when you produce an artifact (like a docker image) that will be deployed to multiple environments, where the configuration is different for each.
Phoenix Presence for Social Networks
How do you track the connection state of multiple users in a social network, where we require scalability and user privacy and where each user's social network is different from the others?
A Module By Any Other Name: Aliases in Elixir
Modules provide a way for us to organize our code and we can alias modules. But when we use aliases, then what are they an alias for?
Documentation as Tests
Rohan describes how you can make your documentation also be the unit tests for your functions.
Multi-Language Flowex Components
This post shows how to use flow-based programming and Erlang ports to connect Ruby, Python and Shell based components in an Elixir application.
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).
