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

Here's what the latest issue looks like:

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

Phoenix/Elixir Testing: Beyond mix test
Great post by Brooklin on how to improve your testing experience by using commands, tags, arguments, and watchers.

Connecting Observer to Production
Mark wrote this post about how he wanted an easy way to run Observer connected to his production environment (and how he achieved it).

An Elixir Adoption Success Story
Great story by Sophie how one small team that was new to Elixir managed to over-deliver on a complex project in just three months.

[video] New in Livebook v0.2: Inputs, Graphs, and More!
José has recorded a video with LiveBook's latest features. Loving it!

Even more from around the Elixir community

TIL: Nested attributes in Phoenix (Live) Views Misc

Vetspire - Senior Software Engineer Misc

Beam Radio: Punking the Servers with Bryan Hunter Podcast

Thinking Elixir: SOLID Elixir with Ilya Averyanov Podcast

Showing off Zig Errors in Zigler Video

Randall Thomas, Keynote, Elixir Wizards Conference 2021 Video

Onboarding to Elixir Blog post

Spot the Difference Blog post

Building a Reminder bot with Elixir Blog post

Where to (not) use Phoenix LiveView Blog post

Pubray — Blogging Powered by Elixir, Phoenix, LiveView and React Blog post

Paycheck, Events, Idempotency and Elixir - What do They Have in Common? Blog post

Three Real-world Examples of Distributed Elixir (pt. 3) Blog post

How to Test WebSocket Clients in Elixir with a Mock Server Blog post

How to Sign raw Ethereum Contract Transactions with Elixir Blog post

Fremantle-industries/rube Project update

KronicDeth/intellij-elixir 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).