ElixirWeekly

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

Here's what the latest issue looks like:

ElixirWeekly by @elixirstatus

Issue #227

Welcome to Issue #227

This issue comes a day late because I thought I had server problems, but it was just PEBKAC. My apologies.

This week in Elixir

Tips for Finch and Telemetry
Claudio provides some quick tips for Finch, Telemetry and Phoenix's LiveDashboard.

Credo Turns 5 & Gets Its First Logo
Credo just got a logo for the first time, celebrating its fifth birthday. Read all about it in this post!

Semaphore CI is Hiring
The fine folks at Semaphore are looking for a Senior Software Engineer to fill an Elixir position on their engineering team (Elixir/Go are their primary languages).

Announcing Muzak (Mutation Testing for Elixir)
Muzak is a mutation testing library for Elixir applications, and Muzak Pro is the full-featured version of Muzak designed for business use.

Announcing AppSignal for Elixir 2.0
AppSignal now saves you more time by making the installation process smoother, instrumenting Ecto out of the box, and giving you better insights by specifying more errors.

Even more from around the Elixir community

Thinking Elixir: Running Migrations in Production with Patryk Bąk Podcast

Things I Wish I can use in React/Javascript from Elixir Blog post

Erlang Term Storage Data Engine in Elixir. How Does It Work? Blog post

Protocols Are Powerful but Beware Blog post

So I Built a Smart Mirror Using Elixir Blog post

Real-time Collaboration with Elixir at Slab Blog post

Getting Bulma CSS to Work with Phoenix LiveView Blog post

How To Upload Files In Elixir Phoenix JSON Api Blog post

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