November 26, 2025
TL;DR meets Ruby’s midlife crisis
Ruby Was Ready from the Start
AI agents, pop-ups, and a comment war over whether Ruby still matters
TLDR: Obie Fernandez argues Ruby’s craft-first ethos and XP make it fit for AI-assisted coding. The comments clap back, saying languages matter less now, “vibe coding” is maddening, and Medium’s pop-up ruins the read—underscoring a bigger fight over hype vs. hard proof in AI-era programming.
Obie Fernandez’s SF Ruby Conf keynote hit Medium with a sweeping thesis: Ruby’s soulful, craft-first roots and Extreme Programming (XP) make it perfect for today’s AI code agents. He recounts ditching “architect” status for hands-on mastery, arguing Ruby was ready from day one. But the comments? Pure fireworks. andrewstuart rolled in with a bucket of ice: languages are less special now thanks to large language models (LLMs), so “who cares” if Ruby is special. alfanick dunked on AI-driven “vibe coding,” saying it feels like babysitting a kid—instant frustration. znpy didn’t even warm up, just dropped the classic “Tl;dr?” like a buzzer beater. Meanwhile, santiagobasulto couldn’t get past Medium’s giant pop-up—turning the reading experience into a UI boss fight. And wiseowise swung the hammer: “snake oil sellers powered by LLM,” demanding substance over another decade of Agile/Xtreme pep talk. The drama boiled down to a culture clash: storytelling and philosophy vs. readers hungry for concrete examples and real demos. A few fans nodded at Ruby’s “soul,” but the louder chorus wanted proof, not vibes—plus a way to read the article without the pop-up. Read the keynote recap here and the original XP book here.
Key Points
- •The article expands on Obie Fernandez’s SF Ruby Conference 2025 keynote focused on XP, AI agents, and Ruby.
- •Fernandez describes his 1997 ambition to become a software architect for status and pay.
- •He critiques mid-1990s practices like UML and Big Design Up Front as insufficient for building resilient software.
- •He argues mastery comes from iterative, hands-on design under pressure and responsibility for outcomes.
- •Encountering Kent Beck’s Extreme Programming reshaped his understanding of effective software development.