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

Here's what the latest issue looks like:

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

Erlang Solving Problems at Scale for 30+ Years
A GOTO unscripted interview about Erlang and how it has been solving problems of scale for 30 years.

Writing Tests in Livebook
Brooklin shows us how to use variables and Kino inputs in ExUnit test modules.

Erlang: the Coding Language that Finance Forgot
Interesting to see a nontechnical article mentioning Erlang and Elixir.

Who Watches Watchmen - Part 1
First article of the series about integrating systemd features with Elixir (and other BEAM languages).

Even more from around the Elixir community

I Have Launched a Free Cast Series: Intro to Elixir Misc

Thinking Elixir: Reviewing Elixir with José Valim - Part 1 Podcast

Elixir Wizards: Brooklyn Zelenka and The Exciting World of Edge Computing Podcast

Elixir Wizards: Meryl Dakin on Changing Lanes and Switching Gears With Elixir Podcast

Elixir na Prática - Introdução Video

Minesweeper - Built with Liveview and Other Recent Tools Blog post

Nx Tip of the Week #9 – Window Functions Blog post

Building a Simple Calendly Clone with Phoenix LiveView (pt. 7) Blog post

Use Rustler with Nerves + Cross-compile Blog post

Building Work Happy: Learning Elixir as a Javascript Developer Blog post

The Origin of the Programming "paradigm" by the Combination of Enum Functions and Pipeline Operators Blog post

The Little Story of Elixir Programming Language Blog post

intellij-elixir/README.md at v12.2.0 · KronicDeth/intellij-elixir Project update

GitHub - NAISorg/conrex: An Elixir Implementation of the CONREC Algorithm for Topographic or Isochrone Maps. 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 :)


Feedback? Questions? Anything else?

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