ElixirWeekly

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

Here's what the latest issue looks like:

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

a11y-audit-elixir: Automated Accessibility Testing for Elixir web Applications Using Axe-core
Angelika wrote a library that integrates axe-core to provide automated accessibility testing in browser-based tests

A RAG for Elixir
This is the second part of a series about using a local RAG (Retrieval Augmented Generation) system for your team’s codebase without leaking any code or data to third parties. In this part, we find out how the LLM (Large Language Model) can read and understand Elixir code and start a conversation about the codebase with the LLM 🤖.

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