ElixirWeekly

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

Here's what the latest issue looks like:

Issue #224

This week in Elixir

Credo 1.5.0 released
This release brings `mix credo diff` and `mix credo --watch`. See the CHANGELOG for a full list of changes.

Compile Elixir Applications into Single Executable Binaries
Bakeware is a new cool tool to compile Elixir apps into single executable, and easily sharable, binaries!

Remote is Looking for Elixir Engineers
Remote is THE global platform that enables companies to employ anyone anywhere. Their Engineering team is expanding and hiring for multiple Elixir roles.

Delivering Social Change with Elixir at Change.org
I really like these case studies on the official Elixir homepage that are getting added.

The BEAM Marches Forward
Lars wrote an informative post about the BEAM and the future of Erlang and Elixir.

Even more from around the Elixir community

Thinking Elixir: Elixir and Art with Milada Majáková Podcast

Elixir Mix: Lumen with Luke Imhoff Podcast

Disassembling Elixir Modules Video

Benchmark XML Parsing Video

Admin Pages with Torch Video

Mutual TLS in Elixir Part 1: HTTPoison Blog post

How to Build a Self-healing System Using Supervision Tree in Elixir Blog post

Elixir Recursion Basics Blog post

Secure Azure Blobs Pre-signing in Elixir Blog post

How IoT Works: Cloud-End (AWS for IoT) Blog post

How to Build a Self-healing System Using Supervision Tree in Elixir Blog post

Incident Project update

b-erdem/absinthe_permission Project update

HTTP Bin Utility Released Project update

My First Elixir Library 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