ElixirWeekly

Issue #209 - Making Audit Logs on Hex.pm Public

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

Here's what the latest issue looks like:

Logo ElixirWeekly by @elixirstatus Issue #209
This week in Elixir

Optimising Data-over-the-wire in Phoenix LiveView
Henrik's post is explores rendering a view with a naive approach, temporary assigns and components, respectively, and compares the payloads.

Making Audit Logs on Hex.pm Public
This post explains why Hex.pm is making its audit logs public and what kind of information you can find via these audit logs. Making Audit Logs on Hex.pm Public - Yiming Chen

Handling Failures in Background Workers with Elixir and Supervisors
Elixir and the Erlang VM allow us to write highly available systems. Does that mean that we don’t have to do anything to make them reliable?

A Case Study for Property Based Testing in Elixir
Ivan wrote up his experience with property based testing in Elixir.

Even more from around the Elixir community

The Changelog: What's Next for José Valim and Elixir? Podcast

ElixirWizards: Chris McCord with a Deep Dive on Phoenix Podcast

ElixirWizards: Council of Wizards with Andrea Leopardi and René Föhring Podcast

ThinkingElixir: ElixirConf 2020 with Jim Freeze Podcast

N-Queens & Backtracking in Elixir Video

Lonestar Elixir 2020 Speaker Talks: Mike Binns - Taming ETS Video

Elixir Berlin July Meetup Video

Building State Machines in Elixir with Ecto Blog post

Vela → time Series Cache Blog post

So Many Ways to Update a Map with Elixir! Blog post

Let's Code: Contact Form in Phoenix Blog post

Headless CMS fun with Phoenix LiveView and Airtable (pt. 2) Blog post

Steffenix/rebalancer Project update

Fremantle-industries/workbench Project update

karolsluszniak/ex_check 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).