ElixirWeekly

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

Here's what the latest issue looks like:

ElixirWeekly by @elixirstatus

Issue #170

Welcome to Issue #170

This issue is a bit short since I am on my way to Code BEAM Lite Berlin.

Next week, we'll be back to our regular programming :-)

This week in Elixir

How Database Transactions Work in Ecto and why Elixir Makes It Awesome?
Read Michal’s article to learn how the functional nature of Elixir helps manage transactional pipelines using Ecto.

How we Improved our Elixir Build Speed by 5x
In this post, Christian explains some of the actions his team took to improve both reliability and speed of our CI build.

Httping - A Phoenix LiveView Demo
Here's 'httping' a Phoenix LiveView application that was going to be Richard's Phoenix Phrenzy submission but he didn't finish in time.

Even more from around the Elixir community

Elixir Outlaws: Refactoring is a Dumb Word Podcast

Elixir Mix: People-Centered Solutions with Travis Elnicky Podcast

Season Two Wrap Podcast

Writing Tests with ExVCR Video

Setting up PrismJS with Phoenix Video

An Elixir/Phoenix Release Workflow for GitHub CI Blog post

What I'm up to - Mostly Elixir Things Blog post

GenServer, Registry, DynamicSupervisor. Combined. Blog post

scenic_layout_o_matic Project update

Kalman Filter Project update

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