ElixirWeekly

Issue #142 - Visual Programming with Elixir: Learning to Write Binary Parsers

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

Here's what the latest issue looks like:

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

Function/Method Look up in Elixir/Ruby
Edison thought GenServer function injections were done through inheritance and discovered the inner workings of defoverridable!

Visual Programming with Elixir: Learning to Write Binary Parsers
Kyle writes about what makes Elixir an unexpected front-runner for learning and prototyping binary protocols.

Teamweek are Looking for a Remote Elixir Backend Developer
It's a fully remote job and 100% Elixir even though the title says Ruby as well. According to Teamweek, it's simply easier to find Ruby devs that want to learn Elixir ;-)

More Readable Repos with the Ecto Filter Pattern
Tyler writes about a great pattern for Ecto query composition he's come across at work.

Building a Small Distributed Elixir Application
Keeping state consistency while running an Elixir application on many servers.

TIL Ecto Constraints vs. Validations
ElixirSchool shows us how Ecto can put validations and constraints onto specific fields to ensure data integrity.

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

Contact

Feedback? Questions? Anything else?

Please contact René Föhring (email or tweet @rrrene for a quick conversation).