It's all about community!
Glad to share Maggie's @exmexconf.bsky.social keynote with everyone!
#ElixirLang
It's all about community!
Glad to share Maggie's @exmexconf.bsky.social keynote with everyone!
#ElixirLang
In Elixir, inner scopes can read outer bindings but can't change them. Once you see that boundary clearly, the common rebinding mistake stops looking like a bug and starts looking like a design.
grox.io/blog/18-scop...
#ElixirLang
A Phoenix LiveView app in 30 minutes sounds like pure leverage, until the βyes loopβ starts and unsolicited features quietly become technical debt.
The first trap is not bad code.
It is unplanned scope that felt reasonable in real time.
Read more -
grox.io/blog/17-the-...
Level up on April 22nd: Full-day ElixirConf EU workshops.
OTP patterns, RAG systems, LLM apps, BEAM internals, AI + Elixir.
Limited spots. @whatyouhi.de @redrapids.bsky.social
Reserve: www.elixirconf.eu#training
Check out the agenda! It's going to be an excellent conference!
See you there!
#ElixirLang
You see = and think assignment.
In Elixir, itβs pattern matching. You describe the shape youβre willing to accept. If it fits, names bind. If it doesnβt, the match fails β and that failure selects the path.
New post:
grox.io/blog/16-patt...
#ElixirLang
We've seen some really good sessions pop into the pile already for Goatmire Elixir. If you have a talk in your heart. Especially if it feels ridiculous, sing it to us:
sessionize.com/goatmire-eli...
#elixirlang
This Master Class is about structured prompting, architectural patterns, and proper oversight. It's about building production-ready systems with AI, not letting AI generate whatever and hoping it works.
You are in charge, not the agent.
Learn with @redrapids.bsky.social
codebeamvancouver.com
I am bringing back VERY DIRECT MESSAGES from 6pm EST to 3am.
How's it work?
Visit the page. Write a message. Hit send. It'll print at my desk on my receipt printer.
Plz RT for fun & be nice.
CC @henryzoo.com @cara.city and other receipt printer dorks
500 issues of Elixir Radar π
- 11 years in a weekly ritual
- 3,000+ pieces of community content featured
- 1,000+ people highlighted
Thank you to everyone who shares their knowledge, our readers, and our sponsors. You make this possible β€οΈ
#ElixirLang
Wow!! Congrats Hugo and thanks for what you do for the community! Amazing!!
The Nerves Starter Kit prototype (right) and the Goatmire name badge (left). The starter kit screen is 50% larger, with higher resolution. They're running the same software, but the starter kit text is smaller due to the higher resolution
Nerves starter kit prototype front view. It has a black 3D printed frame
The Nerves Starter Kit prototype side view. There are two arms that can attach to the back which tilt the display up at a 15Β° angle. The stand can be removed, and instead the whole device can be wall mounted for a picture-frame like experience instead
I had the pleasure of revealing some of the latest updates for the Nerves Starter Kit project last night at the monthly @nervesmeetup.eu! There were some really good discussions, and I definitely woke up today really energized from the feedback we got :)
#Nerves #ElixirLang
Hey! We'd love for you to be with us and there's a Valentine's Day discount going on now for tickets to the conference!
Buy one, get one!
codebeamvancouver.com
#ElixirLang
The problem with AI coding agents isnβt capability. Itβs visibility.
Checkpoint-based workflows fix that. Ask to understand. Plan to align intent. Agent to execute with review. You get full information at every decision point instead of guessing.
New post:
grox.io/blog/15-the-...
#ElixirLang
What could go wrong?
@redrapids.bsky.social talks about why you need to know your tools.
#ElixirLang
youtu.be/ZT0l5yd4MmM
Really looking forward to being in Vancouver for @codebeam.bsky.social in March!
Come join the training and and learn about programming Elixir with AI.
Remember - you are in charge, not the agent!
#ElixirLang
Get tickets: codebeamvancouver.com
In Elixir, choosing a data structure isnβt cosmetic.
Atoms, tuples, lists, and maps each encode different intent and access patterns. The shape you choose affects how your code behaves, reads, and evolves.
New post:
grox.io/blog/14-data...
#ElixirLang
hexdocs.pm/ash_postgres...
Very nifty little #AshFramework extension just released π€― #ElixirLang
π₯Ά βοΈ βοΈ It has been COLD in the US this week. Saturday, Brimson Minnesota was -43ΛF (-42ΛC)
So, until the end of the week, pretty much everything is -43% at the Bookshelf.
Just use coupon code Brrr when you check out.
Stay Warm. Only at pragprog.com
Β
Can you make it??
Also - @redrapids.bsky.social has a great course on Coding Elixir with AI at @groxio.bsky.social - he talks about this issue a lot and how to work with the coding agent. Agents make mistakes - you have to pay attention.
Don't offload your thinking!!!
"The largest gap in scores between the two groups was on debugging questions, suggesting that the ability to understand when code is incorrect and why it fails may be a particular area of concern if AI impedes coding development."
www.anthropic.com/research/AI-...
Oh man. So sorry. Hang in there.
Come join me at @codebeam.bsky.social in Vancouver!
#ElixirLang
People coming from Ruby, Python, or JS often think this defines multiple functions: def greet(:admin), do: "Welcome" def greet(:user), do: "Hello" def greet(_), do: "Hi" It doesnβt. Itβs one function (greet/1) with multiple heads, selected by pattern matching before code runs.
Function Heads are Chosen By Shape
Full blog post:
grox.io/blog/13-func...
#ElixirLang
Hey #ElixirLang folks - any of y'all in MΓ‘laga, Spain? Do you have any suggestions for some meetup/training space for prior to ElixirConf EU in April?
Thanks!!! And yes!
Thanks Max!
Happy new year to all! Weβre starting our 2026 meetup season tomorrow (Wed Jan 14th) at 19h CET via Zoom!
@kevinschweikert.de will be kicking us off with a presentation on using #HomeAssistant with #Nerves and #ElixirLang
Registration link:
nervesmeetup.eu/meetup/kevin...
Here's the thing about working with AI on codebases: You explain an architectural decision carefully. The model seems to understand. Then a few prompts later, it suggests something that quietly breaks the system. The instinct is to prompt better. Longer explanations. More reminders. That's not the fix. The real problem is that the decision only lived in chat. And chat disappears. What works: anchoring decisions in code. Module names that signal responsibility. Function names that encode behavior. Tests that assert boundaries. When intent lives in structure, you stop babysitting the model and start collaborating with it.
New Blog Post: Stop Prompting and Start Anchoring
Read it here:
grox.io/blog/12-stop...
#ElixirLang