Ruby talk with the edges left on.
Remote Ruby follows Ruby developers as they talk through Rails, security, AI tooling, conferences, and the ordinary chaos around the keyboard. The tone is quick and familiar, with technical points landing beside sleepless nights, half-remembered incidents, and dry jokes about uptime.
PRESS PLAY
Remote Ruby is a fast-moving Ruby and Rails conversation show built around programmers thinking in public. It is casual, but not lightweight. Recent episodes start with the texture of real weeks: bad sleep, sick nights, confusing calendars, long meetings, small children, and the sense that Wednesday has already lasted too long. Then the conversation snaps into a Ruby CVE, framework releases, package publishing, authentication changes, and infrastructure habits. The hosts are not named in the metadata, but the recurring dynamic is clear: developers comparing notes from inside software work. Security comes up often. They talk about RubyGems, Bundler, NPM, trusted publishing, GitHub Actions secrets, Homebrew trust, and the uneasy feeling of installing software whose path to the machine is mostly invisible. Performance and caching show up through lived scars, not tidy theory. Redis is discussed alongside the memory of a page made worse by contractors who cached chunks of HTML until nobody could understand the system. AI is another recurring pressure point. The show treats LLMs as useful, sometimes impressive, and often dangerously sloppy when they are allowed to replace understanding. One episode circles around AI-generated pull requests that explain themselves at length while still failing to demonstrate the actual bug. Another praises models that can inspect source code deeply, while insisting that good programmers still have to shape style, constraints, and maintainability. Rails itself remains the anchor. ERB frustrations, browser APIs, Stimulus controllers, Active Job testing, Sidekiq behavior, and the community's appetite for new versions all sit inside the same rolling discussion. Guest episodes bring in community detail, including Jeremy Smith and Joe Peck talking Blue Ridge Ruby, Asheville, consulting gatherings, and long Ruby careers. The show works because it keeps the rough edges in. It sounds like people with context, fatigue, opinions, and enough experience to know when a shiny tool needs a harder question.
Made for: Built for Ruby and Rails developers who enjoy practical ecosystem talk, sharp tooling opinions, and conversations that move from production details to community context without slowing down.
What sets it apart: Remote Ruby stands apart by keeping the thinking process visible. Instead of polished tutorials or headline summaries, it follows developers as they test claims against real workflows, maintenance pain, and recent Ruby community news.
Rubyists having conversations and interviewing others about Ruby and web development.
A broken cache becomes group therapy once you admit the contractors may have won.
Press play if you want
Short reviews from the PlayNext desk, based on the episodes we processed.
A tired week turns into a grounded discussion of package trust, CI secrets, and the limits of MCPs.
Remote Ruby frames a worn-down week as a useful conversation about software trust. The hosts move from Trusted Publishing, leaked package tokens, and GitHub Actions on forked pull requests to the more familiar habit of installing tools through Homebrew, where developers often…
A loose Ruby maintenance discussion finds the hidden engineering cost in uptime promises, cache choices, and newer Rails features.
The episode turns a Ruby maintenance check-in into a sharper look at the costs tucked inside ordinary infrastructure. It moves from a Ruby 3.3 CVE and support windows into uptime math, where the joke about "one nine" lands next to the harder reality that higher availability…
A grounded look at auth maintenance, AI-generated code, and the Rails rough edges developers inherit.
A messy auth-maintenance thread turns into a useful look at software systems that have outgrown their original shape. The conversation tracks older auth code spread across multiple places, a partly finished attempt from months earlier, and the strange imbalance between meeting…
Linux talk with hands-on scars.
Kubernetes changes, explained by the people who made them.
The Remote Ruby hosts cover Rails at Scale Summit prep, including Mike Delecio's Hot Cell sidecar for sandboxing libvips image processing after a recent image-handling vulnerability.
Ruby Central’s long update about September’s maintainers dispute still left the hosts asking what “governance” actually means for RubyGems, Bundler, and the nonprofit itself.
Remote Ruby’s "Memcached Mayhem" covers Ruby 3.3 security maintenance, Rails 8.1.2.1 security fixes, and why Zlib updates landed instead of full Ruby patch releases.
David talks through RubyConf’s CFP review, comparing 97 RubyConf submissions with about 250 RailsConf talks and noting themes like “living with the robots,” “Beautiful Ruby,” and “weird Ruby.” The conversation then moves into AI-assisted debugging, with Mitchell Hashimoto’s Ghostty bug fix and Codex reading GTK source code as the clearest example.
GitHub Actions artifacts were failing with a 404 because two uploaded files had the same executable name.
Claude found Andrew's private Rails method named "action name" overriding Rails' built-in controller method.
Hosts introduce guests Jeremy Smith and Joe Peck, who discuss their involvement in the Ruby community, including organizing Blue Ridge Ruby conference and the Ruby Consultants Quarterly Gathering.