While this is a Cool Thing To See, I do wish things would go the other way—and have all the BI/ML/DS pipelines and workflows folks are building in Python and have them come to Elixir (and, as would follow, Elixir). I get where the momentum is, but having something functional, fault-tolerant, and concurrent underpinning work that’s naturally highly concurrent and error-prone feels like a _much_ more natural fit.
> # WRONG: Elixir has no elsif
How much context is eaten up by skills that rehash what a SOTA model should already know?
Maybe token-wise, it's a wash: Elixir/OTP does a lot without third-party libs, which would require massive npm dependencies to achieve the same thing.
I think most of this trial and error "You are an experienced engineer" stuff probably hurts model performance. No one ever does comprehensive testing so eh, yolo.
https://github.com/agoodway/.claude/blob/main/skills/elixir-...
There are papers showing that models follow instructions less the more instructions they have. Now you think about how many instructions are embedded in that MD + the system prompt + likely a local AGENTS.md and at the end there is probably very little here that matters.
Yeah, I honestly lean on the elixir agent one more over the full skill:
https://github.com/agoodway/.claude/blob/main/agents/elixir-...
Agree, and Claude Code does very well with Elixir despite TS/Python getting all the hype:
https://youtu.be/iV1EcfZSdCM?si=KAJW26GVaBqZjR3M
This helps with keeping it on track writing idiomatic elixir and using good patterns: https://skills.sh/agoodway/.claude/elixir-genius