Rails Business

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 Volume02:17 Cognitive Load Shift04:52 PR Buckets Strategy07:22 Overwhelmed Yet Excited10:36 Workflow Tools Check11:51 Claude Productivity Setup14:02 Second Brain In Practice17:21 Simple Local Files19:30 Automation Limits22:13 Scheduled Script Automation23:00 Claude Cowork vs Command Center23:39 API Permissions and Safety26:12 Claude Code Approval Friction29:25 Subagents and Parallel Work30:44 When Agents Pretend Work34:34 AI Shifts SaaS ThinkingLINKS- Ryan's Website- Brendan's X/Twitter- Brendan's BlueskyQuestions or comments, email us at railsbusinesspod@gmail.comSend us Fan Mail

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 Recap00:43 Conductor Workflow Overview02:40 Parallel Rollbar Fixes04:35 Manual Testing And Setup Hurdles06:33 Debugging With Full Reports08:46 Ports Docker And Dependencies11:50 Parallelism Versus Focus14:57 Closed Loop Trust And Context18:24 Merge Conflicts And Acceptance Gaps22:16 Review Bottleneck And Output Surge25:26 Fixing Gallery Uploads26:39 Multi Select Challenges28:27 Branching Without Conductor31:28 Claude Mobile Workflow32:34 Session Sync Friction34:44 AI Brain For SaaS38:01 APIs And MCP Table Stakes41:49 Internal AI Assistants43:46 Access And Safety Concerns46:31 Second Brain Revival49:03 RAG Tooling Experiments50:04 Wrap Up And Listener FeedbackLINKS- Ryan's Website- Brendan's X/Twitter- Brendan's BlueskyQuestions or comments, email us at railsbusinesspod@gmail.comSend us Fan Mail

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 AI02:31 Why Opus Changed Everything04:55 Claude Max Plans and Limits07:41 Brain Idea and Safety Boundaries09:03 Building the Stack with MCP10:18 Ansible Automation and Deploys12:53 Support Data Summaries in LibreChat15:42 Scheduling Reports to Slack20:17 OpenCode vs Claude and Mobile Workflow23:54 What MCP Connectors Enable26:20 Accessing Brain via Tailscale30:48 Team Size and PR Volume32:32 Claude PR Review Workflow35:25 Conductor Daily Setup38:36 Worktrees and Isolation50:47 Conductor Limits and Pain51:36 App Changes and Scripts54:45 Caddy for Local Domains57:10 Jobs Outlook and WrapNotes- John's X/Twitter- John's Bluesky- John's post setting up conductor with Rails- John's Website- Ryan's Website- Brendan's BlueskyQuestions or comments, email us at railsbusinesspod@gmail.comSend us Fan Mail

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 Testing00:29 From College Web Design to a Niche Opportunity in UST Compliance02:31 Building Opus: A Custom LMS for Gas Station Training03:34 Why Compliance Is Hard: 50 States, 50 Rulebooks04:25 From Training to Past Tools: The Second Product Idea08:06 Two Apps or One? Data Sync, APIs, and Customer Workflows10:25 Would He Do It Again? Decoupling, Upgrades, and Acquisition Optionality12:28 Why Past Tools Is More Complex: Data-Driven Inspections & Asset Inventory16:13 Modeling the Domain in Rails: STI → Delegated Types (and Migration Strategy)22:35 Versioning & “Point-in-Time” Inspections: Preventing Old Reports from Changing24:13 Downtime, SLAs, and Recovering from Form/Data Bugs26:40 Early Scaling Stories: Hardcoding States and Billing Growing Pains29:39 Letting Customers Shape the Product (Beyond Compliance)31:14 Integrations vs. Building Everything In-House32:50 Feature Requests, Backlog Triage, and Adding Sales/Dev Bandwidth37:41 Shipping Without the Never-Ending PR: Iterative Rollouts ("Visits")40:39 Using AI Safely: PRs, Branch Protections, and Documentation Habits46:14 Wrap-Up: Where to Find Kyle and Past TestingLINKS- PASS Testing- Kyle's X/Twitter- Ryan's Website- Brendan's X/Twitter- Brendan's BlueskyQuestions or comments, email us at railsbusinesspod@gmail.comSend us Fan Mail

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 Greetings00:34 Reflecting on the First Year of Podcasting01:57 Memorable Moments and Guest Highlights03:51 Popular Episodes and Themes06:38 Looking Forward: Future Topics and Guests07:42 Balancing Guests and Solo Episodes09:15 Podcast Growth and Marketing Insights10:16 Commitment to Consistency and Goals12:18 Exploring Business and Technical Challenges27:46 Concluding Thoughts and Call for GuestsLINKS- Ryan's Website- Brendan's X/Twitter- Brendan's BlueskyQuestions or comments, email us at railsbusinesspod@gmail.comSend us Fan Mail

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 Up00:34 Exciting News from 37 Signals02:11 The Urge for Clean Code03:33 Challenges in Maintaining Code Quality06:45 Reflections on Code Quality and Team Dynamics16:12 The Role of AI in Coding18:18 AI's Role in Code Architecture18:33 AI in Controller and View Design19:42 AI's Limitations in High-Level Decisions21:13 Using AI for Writing Code and Tests25:09 The Future of AI in Code Readability29:49 Challenges and Hypotheses in AI-Driven Development33:54 Final Thoughts and Future TopicsLINKS- Ryan's Website- Brendan's X/Twitter- Brendan's BlueskyQuestions or comments, email us at railsbusinesspod@gmail.comSend us Fan Mail

In this episode, we chat with Mateus Pereira from Ombu Labs about the nuances of Rails upgrades and how AI is revolutionizing the process. From tackling gem dependencies to client collaboration, Mateus shares valuable insights and tips for executing seamless upgrades. Perfect for developers looking to streamline their Rails projects and leverage AI tools effectively.00:00 Introduction and Casual Chat00:25 Meet Mateus: Senior Rails Engineer01:29 Mateus' Journey into Programming02:17 Joining Ombu Labs: Trials and Triumphs03:33 Lessons from Rejection and Persistence04:35 Challenges in Rails Upgrades08:12 Tackling Gem Dependencies20:04 The Role of AI in Rails Upgrades30:47 Discussing Ruby Critic and Rails Bump32:07 AI in Code Refactoring33:58 Client Relationships and Project Management44:14 Challenges with Test Coverage45:32 Manual Testing and QA Processes49:18 Using AI for Writing Tests55:37 Final Thoughts and Sign-OffLINKS- Mateus' Blog- Mateus' X/Twitter- Mateus' LinkedIn- Ryan's Website- Brendan's X/Twitter- Brendan's BlueskyQuestions or comments, email us at railsbusinesspod@gmail.comSend us Fan Mail

In this episode, Nate Berkopec, the proprietor of Speedshop, a Ruby on Rails performance consultancy, author of several books including the Complete Guide to Rails Performance, and a maintainer of Puma, joins the podcast. Nate discusses his journey into Rails performance optimization, starting from his early career at startups and his breakthrough talk at the Gotham Ruby Conference. He outlines his 'Three S' framework—Speed, Scalability, and Stability—for tackling performance issues. The discussion includes practical advice for Heroku users on optimizing 'dynos' for better request queuing and performance, as well as insights on using tools like JudoScale and PG Analyze for better Sidekiq job management and database optimization. Nate also touches on the importance of setting proper performance thresholds to balance system efficiency and operational costs.00:00 Introduction to Nate Berkopec and Speedshop00:45 Nate's Early Career and Interest in Performance03:36 The Impact of Nate's Conference Talk and Book04:40 Challenges in Diagnosing Performance Issues10:22 Framework for Tackling Performance Problems17:27 Understanding Heroku's Load Balancing27:39 Understanding TCP Open Failures28:10 Optimizing Dynos on Heroku29:16 Setting Performance Thresholds31:12 The Importance of Monitoring and Automation34:25 Challenges with Sidekiq and Data Processing36:24 Best Practices for Sidekiq Queues44:48 Ensuring Job Idempotency and Efficiency49:26 Rapid Fire Tips for Indies52:41 Conclusion and Final ThoughtsLINKS- Speedshop- Nate's X/Twitter- The Complete Guide to Rails Performance Book- Sidekiq in Practice Book- High Availabillity Wikipedia Article- Ryan's Website- Brendan's X/Twitter- Brendan's BlueskyQuestions or comments, email us at railsbusinesspod@gmail.comSend us Fan Mail

In this episode, we tackle the nuances of communicating project requirements within development teams. From managing user stories and acceptance criteria to balancing control and flexibility, we explore best practices for ensuring clarity and efficiency. We share real-world experiences, including the effectiveness of detailed videos and spikes in guiding team members. 01:24 Communicating with Different Levels of Expertise06:06 The Role of Videos in Communication14:45 Challenges in Estimating and Scoping Projects30:52 Using AI to Assist in Writing TicketsLINKS- Ryan's Website- Brendan's X/Twitter- Brendan's BlueskyQuestions or comments, email us at railsbusinesspod@gmail.comSend us Fan Mail

 In this episode, we welcome Stephen Anderson, founder and owner of Bendyworks, a Madison, Wisconsin based Ruby on Rails consultancy. Stephen shares his journey from corporate Java consulting to building a values-driven software shop, discussing his philosophy of constantly seeking 10x productivity improvements and the pivotal moments that led him to entrepreneurship. LINKS- Bendyworks- Ryan's Website- Brendan's X/Twitter- Brendan's BlueskyQuestions or comments, email us at railsbusinesspod@gmail.comSend us Fan Mail