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

Here's what the latest issue looks like:

Logo ElixirWeekly by @elixirstatus Issue #300
Welcome to Issue #300

Holy moly! 300 issues of ElixirWeekly 🎉🎉🎉

Who would have thought?

This week in Elixir

Elixir Style Guide Part 2: Even More Tips and Tricks
What are the other possibilities of organizing, structuring and formatting your Elixir code? This is part 2 of Kamil's guide.

Inflating Git Objects with Elixir
In this post Luis explores inflating Git commit objects using Elixir.

Page Specific Javascript with Phoenix LiveView and Esbuild
Aswin wrote this article on how to split your LiveView Javascript pagewise with esbuild, so your main app.js file stays small.

Using Profiling in Elixir to Improve Performance
In this post, the fine folks from AppSignal explore three profiling tools you can use to find performance issues in Elixir — cprof, eprof, and fprof.

Loosely Coupled Phoenix Contexts
Michael put together a short post about how to achieve low coupling in Phoenix contexts with Kafka!

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