Issue #14: ElixirStatus update, Iteration in Elixir and new Workshops

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

Here's what the latest issue looks like:

This week in Elixir

ElixirStatus now looks like ElixirWeekly
Last week I finally updated ElixirStatus to look a bit more like this newsletter. I really like this "feedback loop" between these sister projects :)

Elixir & Phoenix Workshops
Mike North will be giving Elixir & Phoenix workshops in the near future. Sign up now if you want to learn how to build web apps of a new era!

Iterating in Elixir
Lasse writes about the difference in functional programming when you map, reduce, loop and otherwise iterate data models.

Using Flynn to deploy a Phoenix app
Omar describes how to use Flynn (an open source alternative to Heroku) to deploy your Phoenix application.

Have some side effects in the pipepline
This library provides simple utilities for making side effect calls and return the piped-in value at the end of a pipeline.

A basic introduction to the Actor Model
If you're not sure about the Actor model, you might want to invest 5 minutes to read this introduction of the very basic concepts.

Introducing PhoenixDiff.org
See what changes are needed when upgrading your Phoenix apps. Pretty great idea, might need some time to mature.

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