Your Test Suite Should Hit the LLM, Stop Mocking It
Your test suite should call the LLM API. For real. Not a mock, not a recorded cassette, not a fake that returns canned JSON.
AI and Agentic Engineering in Elixir. Linking processes and people.
Your test suite should call the LLM API. For real. Not a mock, not a recorded cassette, not a fake that returns canned JSON.
Everything I've learned building RAG systems, packaged into one Elixir library. Hybrid search, agentic pipelines, GraphRAG, all running on your existing Ecto Repo and pgvector.
ColBERT-style late interaction retrieval for Elixir. Per-token embeddings and MaxSim scoring for more precise search than single-vector approaches.
Everyone's an AI-assisted developer now. But the range of what that means is absurd.
Addressing the three most valid criticisms of using Elixir and the BEAM for AI agents.
Test LLM outputs by meaning, not by characters. A wave operator for semantic similarity assertions in Elixir, powered by local embeddings.
Python and JavaScript/TypeScript AI frameworks are reinventing what telecom solved in 1986. What 40 years of production-grade concurrency teaches us about building AI agents.
Or why I really hate this shit...