ElixirWeekly

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

Here's what the latest issue looks like:

This week in Elixir

ElixirConf Embedded Round-Up
ElixirConf 2017 was a great opportunity to celebrate what all of us accomplished in the past year. Check out this collection of the Nerves/embedded-related presentations!

5 Great Talks from ElixirConf 2017
Five talks from this year’s ElixirConf US that will teach you something about Elixir development – both for beginners and advanced Alchemists.

Follow-up: Function currying in Elixir
Milton published this post about currying (and potentially uncurrying) functions, which is a follow-post to an article about function currying from 2015.

AlloyCI
This is AlloyCI, a Continuous Integration, Deployment, and Delivery coordinator, written in Elixir, that takes advantage of the GitLab CI Runner to prepare and run your pipelines.

Cloudinex
Cloudinex is an Elixir wrapper around the Cloudinary Image Upload API and Admin API using Tesla.

ElixirSchool: Benchmarking with Benchee!
This is a lesson on benchmarking in Elixir with Benchee! Learn just how easy it is to get real answers on how fast your functions are.

Sengoku Game
Steve built a risk-like strategy game, taking place in feudal Japan, in Elixir. He is currently introducing computer AI powered opponents.

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