ElixirWeekly

Issue #286 - Events, Event Sourcing, and the Path Forward

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

Here's what the latest issue looks like:

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

Getting Started with Axon
Sean wrote this deep dive into Axon and Nx about the basics of machine learning and neural networks.

Events, Event Sourcing, and the Path Forward
Karl wrote about their ~2.5 yrs experience at Community building a fully evented system with event sourcing, archives, replays, etc.

Build Interactive Phoenix LiveView UIs with Components
Learn how to make use of functional components to create complex Phoenix LiveView UIs with Sophie.

Meaningful Config Keys in Elixir Projects
A quick reminder by Remi that using a meaningful keys to store configuration in Elixir is quite simple and often leads to more maintainable code.

Passing Unknown Attributes into Your Component
Mark shows us how to pass arbitrary attributes into a given LiveView component.

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