ElixirWeekly

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

Here's what the latest issue looks like:

ElixirWeekly by @elixirstatus

Issue #204

Welcome to Issue #204

These are challenging times. I think most of us could benefit from a moment of silent introspection at this point.

Stay safe.

Even more from around the Elixir community

TIL: Elixir Date and Time conversion into US standards Misc

SEO Friendly URLs Revised Video

Lonestar Elixir 2020 Speaker Talks: Justin Schneck - Responsible Resources Video

Pattern Matching With Todd - Michael Crumm Podcast

Elixir Mix: Adopting Elixir at FindHotel with Fernando Hamasaki de Amorim Podcast

Steve Bussey on Real-Time Applications Podcast

Pattern Matching With Todd - Michael Crumm Podcast

Notes on Code BEAM V 2020 Blog post

Elixir Processes: Observability Blog post

TypedStruct 0.2.0: Plugin Interface Blog post

Elixir Community Tools: StreamData Blog post

The Repository Pattern, Ecto, and Database-less Testing Blog post

Productivity, Maintainability and Performance with Elixir & Functional Programming Blog post

The Repository Pattern, Ecto, and Database-less Testing Blog post

Elixir and ETS Alchemy Blog post

Telemetría Blog post

Gleam v0.9 Released! – by Otter Nonsense Blog post

Emacs Setup for Elixir Blog post

Stream in Elixir Blog post

Elixir-wallaby/wallaby Project update

Dwyl/phoenix-todo-list-tutorial Project update

Telemetria got Zero-config and Annotations 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).