ElixirWeekly

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

Here's what the latest issue looks like:

Issue #72

This week in Elixir

Badges & Elixir: Using Behaviours
Svilen and his team used Elixir’s Behaviours to build an internal API for badges (which his startup is all about).

Side projects in Elixir
Jason wrote a blog post about doing side projects in Elixir. It discusses the proper mindset for approaching side projects, finding ideas, and planning.

Structuring Elixir projects
Hubert wrote a love letter to OTP applications and umbrella projects on his company’s blog.

Exceptions in Elixir
Vitaly investigates how, in Elixir applications, exceptions are regularly thrown but rarely caught.

Refactoring Composable Queries with Ecto
Robert wrote this article on bringing a modular approach to how we craft queries make complex requests simple.

Even more from around the Elixir community

ElixirTalk - Storing State in Elixir Apps Podcast

Hands on Training: Learn to Create Phoenix from Scratch Conference

Talk on The Story of Conn at Opencamps NYC Conference

About Ups and Downs of Both Ruby and Elixir Blog post

Deploying Elixir applications with Docker Blog post

Quick & Easy Elixir Refactorings - Part 1 Blog post

Roman Numerals Kata in Elixir with Pattern Matching Blog post

Deploying an Elixir + Phoenix + Elm with Nanobox Blog post

How to Add Concurrent, Transactional End-To-End Tests in a Phoenix-Powered Ember App Blog post

json_stream_encoder v0.1.2 Project update

plymio_ast_vorm v0.1.0 Project update

plymio_option v0.3.0 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).

ElixirWeekly by @elixirstatus

ElixirWeekly

Questions & Answers

Contact