In this episode of On Rails, Robby is joined by Hilary Stohs-Krause, a Senior Software Engineer at Red Canary. They explore how engineering teams approach everyday performance work, from small Active Record optimizations to larger architectural decisions. Hilary shares insights from Red Canary's journey switching from React to Rails' native Hotwire stack, how her team tackled flaky test failures that were slowing down continuous deployments, and some strong opinions about custom linters.
π§° Tools, Libraries, and Books Mentioned
- RuboCop β Enforces Ruby style and conventions, with support for custom cops.
- haml-lint β Linter for HAML templates to enforce consistent view code.
- ESLint β JavaScript linter used for maintaining consistent code quality, especially in React.
- HadoLint β Linter for Dockerfiles to catch common issues and enforce best practices.
- SitePrism β Page-object model DSL for Capybara to reduce flaky system tests.
- Sidekiq β Background job processor used in production Rails environments.
- Turbo β Part of the Hotwire stack for reactive updates without full-page reloads.
- Stimulus β Lightweight JavaScript framework for enhancing HTML with small interactions.
- Hotwire β A set of tools (Turbo + Stimulus) for building modern web apps without heavy JavaScript.
- Thinking in Bets β A book about better decision-making under uncertainty, by Annie Duke.
Send us a text
On Rails is a podcast focused on real-world technical decision-making, exploring how teams are scaling, architecting, and solving complex challenges with Rails.
On Rails is brought to you by The Rails Foundation, and hosted by Robby Russell of Planet Argon, a consultancy that helps teams improve and modernize their existing Ruby on Rails apps.
