Rails Business

Brendan Buckingham & Ryan Frisch

Brendan Buckingham and Ryan Frisch talk about developing with Ruby on Rails and how to leverage it to build a business.

  1. -5 J

    Do Pull Request Reviews Still Matter in the Age of AI?

    The hosts once again discuss the recurring theme of AI’s impact on development workflows.  They discuss various topics, including:  Increased PR volume from AI-assisted coding and whether traditional pull request reviews are still necessary. Should AI be used earlier for pre-PR review and stronger CI guardrails for performance and security. What is the role of automated testing, and are they even more important as code generation accelerates?01:05 PR Reviews Under AI Load 02:38 What PR Review Is For 05:02 Human Review What Remains 08:36 AI Pre Review And PR Purpose 11:01 Guardrails CI Performance Security 12:39 TDD Tests As Behavior Spec 15:53 AI Versus Automation In Pipeline 19:17 Testing Evolution Unit Vs System 20:32 Feature Specs And Functional Review 21:35 Bugs vs Defects Focus 23:37 Smoke Tests for Upgrades 24:44 Controller Tests Debate 27:40 Test Pyramid and Frontend Gap 28:37 Refactoring for Unit Tests 30:57 AI Coding Raises Review Stakes 34:00 Claude MD Friction 35:54 Wrap Up and Testing Habit LINKS Justin Searls PodcastWorking Effectively with Legacy Code Book by Michael FeathersProfessional Rails Testing: Tools and Principles Book by Jason SwettRyan's WebsiteBrendan's X/TwitterBrendan's BlueskyQuestions or comments, email us at railsbusinesspod@gmail.com Send us Fan Mail

    39 min

  2. 16 AVR.

    Building with an AI Orchestrator Workflow

    In this episode, the hosts discuss building a “universal scraper” for event calendars and a new AI-assisted workflow using a long-running orchestrator.md thread. 00:12 Why Change AI Workflow 01:29 Orchestrator File Setup 04:36 How Memory Persists 07:33 Platform Constraints WSL 08:45 Git Worktrees and Isolation 12:07 Scraper Build Approach 18:26 Incremental TDD Development 20:17 Making It Truly Universal 22:39 Universal Scraper Explained 26:03 Wrap Up and Next Steps LINKS - Ryan's Website - Brendan's X/Twitter - Brendan's Bluesky Questions or comments, email us at railsbusinesspod@gmail.com Send us Fan Mail

    29 min

  3. 2 AVR.

    AI Coding at Scale: Managing PR Overload, Using Claude to Stay Organized and Rethinking SaaS for an AI-First World

    The hosts discuss how AI-assisted coding has massively increased their output, creating a new bottleneck: cognitive load, PR review, testing, and getting work shipped. Ryan discusses splitting time between finishing near-complete work, advancing a few large architectural initiatives, and handling ongoing support.  Brendan talks about his productivity system using Claude to manage his time using local markdown files to help stay on top of things. They also cover risks of AI automation, permission scoping, subagent/approval bugs, and conclude with a renewed optimism that AI raises abstraction, increases competition, and pushes SaaS to adapt via execution, moats, and AI-ready APIs. 00:27 AI Code Volume 02:17 Cognitive Load Shift 04:52 PR Buckets Strategy 07:22 Overwhelmed Yet Excited 10:36 Workflow Tools Check 11:51 Claude Productivity Setup 14:02 Second Brain In Practice 17:21 Simple Local Files 19:30 Automation Limits 22:13 Scheduled Script Automation 23:00 Claude Cowork vs Command Center 23:39 API Permissions and Safety 26:12 Claude Code Approval Friction 29:25 Subagents and Parallel Work 30:44 When Agents Pretend Work 34:34 AI Shifts SaaS Thinking LINKS - Ryan's Website - Brendan's X/Twitter - Brendan's Bluesky Questions or comments, email us at railsbusinesspod@gmail.com Send us Fan Mail

    42 min

  4. 19 MARS

    Scaling AI-Assisted Development

    Today we discuss lessons from our previous episode with John Nunemaker, focusing on the Conductor tool and how multi-workspace, multi-agent workflows can speed up coding and bug fixing. Brendan shares his experimenting with parallelizing six Rollbar error fixes at once by generating prompts and running them in separate Conductor workspaces. They compare this with a one-agent-at-a-time workflow and debate whether closed-loop setups (ports, databases, dependencies) could make parallel work trustworthy and reduce context-switching costs. They also cover using full Honeybadger/XML reports for faster debugging, using Claude Code from a phone to create PRs, challenges syncing session history, and broader AI product strategy like APIs/MCP, and RAG. 00:00 Catch Up And Recap 00:43 Conductor Workflow Overview 02:40 Parallel Rollbar Fixes 04:35 Manual Testing And Setup Hurdles 06:33 Debugging With Full Reports 08:46 Ports Docker And Dependencies 11:50 Parallelism Versus Focus 14:57 Closed Loop Trust And Context 18:24 Merge Conflicts And Acceptance Gaps 22:16 Review Bottleneck And Output Surge 25:26 Fixing Gallery Uploads 26:39 Multi Select Challenges 28:27 Branching Without Conductor 31:28 Claude Mobile Workflow 32:34 Session Sync Friction 34:44 AI Brain For SaaS 38:01 APIs And MCP Table Stakes 41:49 Internal AI Assistants 43:46 Access And Safety Concerns 46:31 Second Brain Revival 49:03 RAG Tooling Experiments 50:04 Wrap Up And Listener Feedback LINKS - Ryan's Website - Brendan's X/Twitter - Brendan's Bluesky Questions or comments, email us at railsbusinesspod@gmail.com Send us Fan Mail

    51 min

  5. 5 MARS

    John Nunemaker on AI Development

    John Nunemaker returns to discuss how fast AI tooling has changed and argues tech leaders should adopt Claude Max (defaulting to Opus), set up agent-friendly local environments, and roll that out to their teams. He shares how his company built an internal “brain” using LibreChat as a self-hosted interface, enabling non-engineers to query company data and generate insights like weekly support summaries from various sources. The conversation also covers worktrees and Conductor for parallel, isolated dev environments. 01:22 Tech Leaders Must Adopt AI 02:31 Why Opus Changed Everything 04:55 Claude Max Plans and Limits 07:41 Brain Idea and Safety Boundaries 09:03 Building the Stack with MCP 10:18 Ansible Automation and Deploys 12:53 Support Data Summaries in LibreChat 15:42 Scheduling Reports to Slack 20:17 OpenCode vs Claude and Mobile Workflow 23:54 What MCP Connectors Enable 26:20 Accessing Brain via Tailscale 30:48 Team Size and PR Volume 32:32 Claude PR Review Workflow 35:25 Conductor Daily Setup 38:36 Worktrees and Isolation 50:47 Conductor Limits and Pain 51:36 App Changes and Scripts 54:45 Caddy for Local Domains 57:10 Jobs Outlook and Wrap Notes - John's X/Twitter - John's Bluesky - John's post setting up conductor with Rails - John's Website - Ryan's Website - Brendan's Bluesky Questions or comments, email us at railsbusinesspod@gmail.com Send us Fan Mail

    58 min

  6. 19 FÉVR.

    Kyle Keesling

    In this episode, Kyle Keesling, co-owner of PASS Testing and long-time solo Rails developer, shares how PASS grew from a college web design side project into a niche software and training business for the Underground Storage Tank (UST) industry. The conversation covers why they kept the products as two apps connected by a read-only private API, what makes compliance software hard, and how they modeled flexible equipment and inspection data—evolving from STI to Rails delegated types. Kyle also discusses early scaling pains around billing and payments, how feature requests are prioritized with help from their CRO and a contractor, and how tools like Claude Code are changing his workflow while maintaining PR-based review and safer deployment practices. 00:00 Meet Kyle Keesling& His Role at PASS Testing 00:29 From College Web Design to a Niche Opportunity in UST Compliance 02:31 Building Opus: A Custom LMS for Gas Station Training 03:34 Why Compliance Is Hard: 50 States, 50 Rulebooks 04:25 From Training to Past Tools: The Second Product Idea 08:06 Two Apps or One? Data Sync, APIs, and Customer Workflows 10:25 Would He Do It Again? Decoupling, Upgrades, and Acquisition Optionality 12:28 Why Past Tools Is More Complex: Data-Driven Inspections & Asset Inventory 16:13 Modeling the Domain in Rails: STI → Delegated Types (and Migration Strategy) 22:35 Versioning & “Point-in-Time” Inspections: Preventing Old Reports from Changing 24:13 Downtime, SLAs, and Recovering from Form/Data Bugs 26:40 Early Scaling Stories: Hardcoding States and Billing Growing Pains 29:39 Letting Customers Shape the Product (Beyond Compliance) 31:14 Integrations vs. Building Everything In-House 32:50 Feature Requests, Backlog Triage, and Adding Sales/Dev Bandwidth 37:41 Shipping Without the Never-Ending PR: Iterative Rollouts ("Visits") 40:39 Using AI Safely: PRs, Branch Protections, and Documentation Habits 46:14 Wrap-Up: Where to Find Kyle and Past Testing LINKS - PASS Testing - Kyle's X/Twitter - Ryan's Website - Brendan's X/Twitter - Brendan's Bluesky Questions or comments, email us at railsbusinesspod@gmail.com Send us Fan Mail

    47 min

  7. 5 FÉVR.

    Reflecting on Our First Year of the Podcast

    In this episode, the hosts reconnect after a holiday break to reflect on their podcast journey over the last year. They discuss important milestones like their one-year recording anniversary, the various episodes from the past year, and sharing their favorite moments. 00:00 Introduction and New Year Greetings 00:34 Reflecting on the First Year of Podcasting 01:57 Memorable Moments and Guest Highlights 03:51 Popular Episodes and Themes 06:38 Looking Forward: Future Topics and Guests 07:42 Balancing Guests and Solo Episodes 09:15 Podcast Growth and Marketing Insights 10:16 Commitment to Consistency and Goals 12:18 Exploring Business and Technical Challenges 27:46 Concluding Thoughts and Call for Guests LINKS - Ryan's Website - Brendan's X/Twitter - Brendan's Bluesky Questions or comments, email us at railsbusinesspod@gmail.com Send us Fan Mail

    31 min

  8. 22 JANV.

    Striving for Ideal Code

    In this episode, the hosts discuss reflect on the high-quality, maintainable code found in various videos and books and their own aspirations to emulate such coding standards. The conversation covers the challenges of maintaining good coding practices over time and under business pressures. They explore the concept of 'good enough' code based on the maturity stage of a business, and debate how AI impacts coding quality. The hosts consider how AI can assist in writing tests, potential pitfalls, and the complexity of integrating AI into development while maintaining high standards. Lastly, they touch upon the concept of agentic coding and the importance of well-defined code boundaries in future development strategies. 00:00 Introduction and Catching Up 00:34 Exciting News from 37 Signals 02:11 The Urge for Clean Code 03:33 Challenges in Maintaining Code Quality 06:45 Reflections on Code Quality and Team Dynamics 16:12 The Role of AI in Coding 18:18 AI's Role in Code Architecture 18:33 AI in Controller and View Design 19:42 AI's Limitations in High-Level Decisions 21:13 Using AI for Writing Code and Tests 25:09 The Future of AI in Code Readability 29:49 Challenges and Hypotheses in AI-Driven Development 33:54 Final Thoughts and Future Topics LINKS - Ryan's Website - Brendan's X/Twitter - Brendan's Bluesky Questions or comments, email us at railsbusinesspod@gmail.com Send us Fan Mail

    34 min
Tout afficher (32)

À propos

Brendan Buckingham and Ryan Frisch talk about developing with Ruby on Rails and how to leverage it to build a business.

Informations

  • Création
    Brendan Buckingham & Ryan Frisch
  • Années d’activité
    2025 - 2026
  • Épisodes
    32
  • Classification
    Contenu explicite
  • Copyright
    © 2026 Rails Business
  • Site web de l’émission
    Rails Business

Vous aimeriez peut‑être aussi