DiscoverThe Ruby on Rails Podcast
The Ruby on Rails Podcast
Claim Ownership

The Ruby on Rails Podcast

Author: David Hill

Subscribed: 1,285Played: 21,144
Share

Description

The Ruby on Rails Podcast, a weekly conversation about Ruby on Rails, open source software, and the programming profession. Edited by Redrum Creative.
561 Episodes
Reverse
What makes a Ruby conference memorable—and what does it take to organize one? Adrian Marin joins David Hill to share lessons from creating Friendly.rb as David prepares to launch Ruby Magic in Orlando. They discuss finding sponsors, choosing a venue, balancing invited speakers with a CFP, and making room for the hallway conversations that turn fellow attendees into lasting friends. Adrian also shares the story behind Avo, the Rails application-building toolkit he started after seeing how Laravel Nova accelerated his team’s work. He describes turning an almost-abandoned project into his full-time business and overcoming developers’ skepticism about admin tools by emphasizing extensibility and escape hatches. The conversation turns to AI’s impact on both development and the business of selling software. Adrian explains how his team uses AI to tackle more features and difficult problems, alongside adding AI capabilities to Avo itself. He also speaks candidly about customer churn and stagnant growth, while he and David examine the ongoing maintenance, authorization, and security responsibilities behind software that can seemingly be generated in minutes. Finally, Adrian recounts how the Ruby Passport grew from an idea shared among conference friends into thousands of physical passports distributed around the world. From custom stamps and NFC chips to RubyEvents.org integration, the project gives Rubyists a way to collect memories, record their conference travels, and stay connected across events. Links Ruby Events Avo Ruby Magic Sponsors Ruby Native, by Joe Masilotti: https://rubynative.com/david AppSignal: https://appsignal.com/rubyonrailspodcast Special thanks to Flagrant for the new logo and header images for the podcast!
What does it take to make an open source project welcoming to contributors—and manageable for its maintainers—in the age of AI? Rachael Wright-Munn joins David Hill to share what she’s learning through her work on Ruby Events, where supporting new contributors and reviewing AI-assisted pull requests raise many of the same questions about context, documentation, and code quality. Rachael explains how Ruby Events uses YAML validation to catch problems and provide actionable feedback, along with an evolving Active Record–style interface built around Yerb. The conversation explores how clear rules, useful abstractions, and better development environments can help contributors produce changes that are easier to review and merge, while reducing the pressure on volunteer maintainers. They also discuss Rachael’s experiments with Orca, parallel Git worktrees, and reviewing contributions from her phone. From carving out small pull requests to getting agents to attach screenshots, Rachael shares both the possibilities and the practical frustrations of building an AI-assisted workflow—and why human judgment and an understanding of the code remain essential. David shares his early plans for Ruby Magic, a Ruby conference in Orlando, prompting a conversation about why gathering as a community still matters as development tools change. The episode closes with reflections on learning in public, living with anxiety, and expanding your comfort zone by taking on work that feels intimidating. If you're interested in learning more about Ruby Magic as it develops, sign up here: https://rubymagic.dev/ Sponsors Ruby Native, by Joe Masilotti: https://rubynative.com/david Judoscale: https://judoscale.com Special thanks to Flagrant for the new logo and header images for the podcast!
What happens when the tool you rely on disappears? For Eduardo and Camila Souza, the shutdown of Pivotal Tracker became the motivation to build Pivotal Tasker, a Rails-based alternative inspired by the project management workflow they missed. They discuss reconstructing the experience from memory and reference material, adding classic and modern interfaces, and integrating coding agents to help create and work through stories. The conversation expands into their move from consulting toward building products. Eduardo and Camila describe Chamber Builder, an all-in-one platform for chambers of commerce, and a custom sales CRM that brings calling, recordings, transcripts, and AI-generated follow-up suggestions into the browser. Across these projects, they explain how observing real workflows reveals opportunities to replace expensive, fragmented tools with simpler software. AI helps their small team move faster, but they remain firm about reviewing its output and keeping their applications understandable and maintainable without it. They discuss setting technical guardrails, refining generated interfaces, and using Camila’s business background to make software easier for customers to navigate. They also share lessons from getting products into customers’ hands, including offering free data migration, demonstrating redesigned websites with prospective customers’ own public information, and switching to direct outreach when advertising failed to produce results. Along the way, Eduardo describes an internal deployment tool built around Kamal, and the pair reflect on how AI is changing both consulting work and the opportunities available to Rails developers. Links Pivotal Tasker: https://pivotaltasker.com ChamberBuilder: https://chamberbuilder.com/ Unlok Labs: https://unloklabs.com/ Sponsors Ruby Native, by Joe Masilotti: https://rubynative.com/david Judoscale: https://judoscale.com Special thanks to Flagrant for the new logo and header images for the podcast!
JP Camara joins the show to explore background job coordination, real-time collaboration, and the opportunities he sees for Ruby and Rails as AI changes how developers work. First, JP shares the story behind bringing batches to Solid Queue, from an early proposal to the conference conversations and community interest that helped move the feature forward. He explains how batches let developers treat a group of jobs as a unit, track success and failure, and trigger callbacks when processing finishes—making it easier to coordinate workflows that span many background jobs. JP also discusses the implementation challenges behind the feature, including database transactions, jobs deferred until a transaction commits, and reducing the performance overhead of tracking batches. He describes his related work on Mission Control Jobs, which gives developers a visual way to inspect batch progress, investigate failures, and find the jobs involved. The conversation then turns to YRBY, JP’s project for adding real-time collaborative editing to Rails applications. He explains how conflict-free replicated data types, or CRDTs, support Google Docs-style collaboration, and how Ruby bindings to a Rust library let him integrate with Action Cable or AnyCable without requiring a separate Node.js server. He also discusses editor integration, encrypted collaborative text, and his work on allowing AI agents to participate alongside people in shared documents. Finally, JP reflects on how AI helps him maintain momentum on open source projects while balancing a full-time job and family responsibilities. He shares how his team at Wealthbox uses RubyLLM, why its expressive interface makes working with different AI providers more approachable, and why he believes there is still plenty of valuable work ahead for the Ruby and Rails ecosystem. YRBY - https://yrby.dev lexxy-realtime - https://github.com/jpcamara/lexxy-realtime/tree/main RubyLLM - https://rubyllm.com/ Sponsor AppSignal: https://appsignal.com/rubyonrailspodcast
What does it mean to be a software developer when writing code is no longer the central part of the job? Jessica Kerr and Avdi Grimm join David Hill for a conversation about the changing work of software engineering—and how to navigate that change without losing the curiosity, satisfaction, and human connection that drew us to it. They begin by examining why AI-assisted programming differs from AI-generated art and entertainment, including the role of tests and measurable feedback in evaluating software. From there, Jessica and Avdi discuss the challenge to developer identity when tools can handle more of the implementation, and the opportunities that opens for building useful things, exploring neglected projects, and focusing on product decisions. The conversation gets practical with a look at overseeing AI-generated code. Avdi describes his use of specialized reviewer agents and repeated auditing, while Jessica explains how developers can define correctness, provide feedback loops, and get clearer visibility into changes. They also explore why inconsistent code and technical debt create friction for agents, and how token usage and evaluations can help measure the cost of that friction and compare different development approaches. Beyond implementation, David, Jessica, and Avdi discuss using AI as a tutor, expanding into design and product work, and the renewed value of design patterns and domain-driven design as shared vocabulary for communicating with agents. They also consider what developers can learn from people who began coding with AI, rather than assuming how those newcomers will learn. Throughout the episode, one question keeps returning: how can these tools create more time for people? From board games and conferences to conversations about what customers actually need, Jessica and Avdi make the case for using AI to support richer human collaboration—and keeping it from becoming a substitute for it. Sponsor: AppSignal: https://appsignal.com/rubyonrailspodcast
loading
Comments