I had never personally worked with embeddings, vector databases, or retrieval-augmented generation before this project. I knew the words. I did not know where the sharp edges were. Folks on our team do… but I felt it was time to wrap my own head around it.
What I did have was a real problem, a team that loves Ruby, and enough curiosity to see where things broke.
This is the story of that experiment… what worked, what surprised me, and what I’d tell another Ruby developer who’s considering something similar.
The Problem
At Planet Argon, we manage several client projects. We live in Jira (I know… I know…). We keep decisions in Confluence. We ship code from GitHub. Over years a lot of…





Pluggable Garbage Collectors in Ruby: Exploring the New Modular GC API
Processing documents into structured data





Rendering Maps by Name: Symbolic Geographic Extents in Ruby


The Universal Pain: Waiting for CI Every Rails developer eventually reaches enlightenment — not through meditation, but …
From 30 Minutes to 2: Speed-Running Rails CI (Without Cheating… Much)
…



Person in parachute over mountains during daytime

