ElixirWeekly

E-Mail

can't be blank

Making sure you're human: Name your favorite Elixir kernel module!

(can't be blank)

Subscribe

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

Here's what the latest issue looks like:

ElixirWeekly by @elixirstatus

Issue #187

This week in Elixir

Expecting the Unexpected in Elixir
What can one 50 year old cryptic error message teach us about the software we write today?

The Dashbit Blog & How It was Made!
The first blog post by Dashbit shows how José and colleagues implemented the blog itself, using some neat Elixir and Phoenix features!

Elixir’s with Statement is Fantastic
This post by Alex describes how to tame one of Elixir’s most powerful constructs and write concise code that’s easy to read, maintain, and debug.

Phoenix LiveView JavaScript Hooks and Select2
Alvise published this post about LiveView and Select2 with JS Hooks.

Even more from around the Elixir community

ElixirWizards: Sophie DeBenedetto and Meryl Dakin Podcast

ElixirTalk Feat. Bruce Tate Podcast

Phoenix LiveView 0.6.0 Video

Simple Phoenix LiveView App: Planning DB Schemas Video

Setup Phoenix with Svelte+Rollup Blog post

How to use Elixir Phoenix with Janus WebRTC Blog post

Internationalisation with Phoenix Live Layouts Blog post

Monitoring the Erlang VM With AppSignal's Magic Dashboard Blog post

Credo v1.2.2 released Project update

Evadne/packmatic Project update

meltwater/gen_rmq Project update

bechurch/auth0_jwks Project update

Crbelaus/trans Project update

KronicDeth/intellij-elixir 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:

E-Mail

can't be blank

Making sure you're human: Name your favorite Elixir kernel module!

(can't be blank)

Subscribe

Questions & Answers

Yes! Simply post them to ElixirStatus and you can be sure that they land on my radar.

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.

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

Please contact René Föhring (email or tweet @rrrene for a quick conversation).