ElixirWeekly

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

Here's what the latest issue looks like:

ElixirWeekly by @elixirstatus

Issue #75

Welcome to Issue #75

Due to a business trip on Thursday, this issue follows a style best described as "short form". Enjoy!

This week in Elixir

Shuffled Records in Phoenix
Nathan shares a way to get shuffled records from the database via Ecto/Phoenix.

Macro Madness: How to use `use` well
Macro extravaganza explained by DockYard's own Luke Imhoff!

[BOOK] Phoenix for Rails Developers
Elvio just published the book “Phoenix for Rails Developers”! Use the promo code "elixirstatus" to get a 10% OFF discount!

Sage - Sagas pattern in pure Elixir
Sage is an dependency-free implementation of Sagas pattern in pure Elixir. It’s like Ecto.Multi but across business logic and third-party APIs.

The Secret Behind Elixir Operator Re-Definitions: + to -
This article comprises things like creating new definitions for existing operators.

Three tutorials covering deploying Phoenix apps to Google Cloud
For those interested in deploying an Elixir/Phoenix app to Google Cloud, Daniel has posted three getting-started tutorials on Google’s community site.

Even more from around the Elixir community

Pattern Matching in Elixir Video

Property-based Testing is a Mindset Talk slides

Elixir: Anonymous Functions - A Taste of Functional Programming Blog post

Writing a Command Line app in Elixir | What did I Learn Blog post

Generating Sequences with Elixir Streams Blog post

Ten Things I Wish I Knew Before Using Elixir Blog post

Looking for feedback about stdlib Logger improvements! Project update

Submit your blog post/project update

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