TDD With Claude Code in Elixir: What Holds Up
Where TDD with Claude Code actually holds up in an Elixir/Phoenix codebase (ExUnit async, mix precommit, Ecto.Multi idempotency) and where it breaks.
We can't find the internet
Attempting to reconnect
Something went wrong!
Attempting to reconnect
Writing · Tag
55 posts on engineering, page 4 of 5. Or browse the full writing index →
Where TDD with Claude Code actually holds up in an Elixir/Phoenix codebase (ExUnit async, mix precommit, Ecto.Multi idempotency) and where it breaks.
Your agent's tools need your production keys; the agent itself never should. The broker pattern, per-tool scoping, and what a five-person team can skip.
Classic SRE postmortems can't explain agent incidents. The sections to add (decision-time context, autonomy rung, permissions delta), with a template.
The Claude Code plugins that earn a permanent slot in my stack, sorted by what they actually change: my process, my domain expertise, or just friction.
An homage to Peter Welch's Programming Sucks, updated for agents: a genius intern with amnesia, hallucinated packages, and a closet that eats your auth layer.
The path to senior ran through the grunt work AI now does in one prompt. The knowing-vs-doing gap hits juniors first, and here's how to grow architects anyway.
Professionalism in software is owning the whole outcome: the cost, the failure, the 3am page, the wrong call. Process and titles don't cover it.
A Tencent benchmark across 20 languages found Elixir at the top of LLM code-completion rates: Claude Opus 4 hit 80.3% on Elixir vs 74.9% on C#. The reasons are the same boring properties that have always made Elixir pleasant, now compounded by AI.
async/await and goroutines solve scheduling. The BEAM solves failure. Why most concurrency pain is actually failure-isolation pain, and only the actor model plus supervision trees fix it.
Open the repos behind the agent tooling you run (Ollama, the MCP SDKs, the orchestration engines) and it's all Go. The reason is that an agent tool is a concurrent network daemon that ships as one binary.
The "is Ruby dead" obituary runs every year and confuses hype velocity with shipping velocity. Rails 8 deleted the actual reasons people left: Redis, Sidekiq, the Node build step.
Migrating an AI-first product from GCP to Azure cut $350K from infrastructure spend over six months. The negotiation that mattered more than the architecture, the $50K we accidentally cost ourselves back, and the four migrations I'd refuse to do today.