Bug-Driven Development
summary
A real bug report about an API mismatch drives a concrete fix: reproduce with RSpec and FactoryGirl, discover a missing assignment that leaks role and enabled between accounts because Rails loads associations by Ids and the app uses UUIDs. The team replaces Ruby-side searching with a clearer design: a UserAccountDecorator plus a SearchUserAccounts loader, adds a focused loader spec, and ships the refactor to eliminate the leak and prevent regressions.
AI-written summary · about
chapters (11)
- 0:00Intro
- 0:14Pain Free Rails 66 Deployments
- 0:50PROCORE
- 1:44When setting a user as inactive, the change is not reflected correctly in the API
- 2:22The bug is confirmed, but only for accounts in the EU region
- 3:04I can only recreate on staging environment with an enterprise account
- 6:34The Missing Character
- 13:47Loading more from the database is faster.
- 20:49Where do I put the regression test?
- 23:23A bug is an opportunity for improvement
- 25:26Better design: Abstractions, not just indirection
related talks
25mRefactoring: The ASMR of Programming Talks
35mThe worst Ruby codes I've seen in my life
27mFake Your Test Away: How To Abuse Your Test Doubles
34mEliminating Inconsistent Test Failures
32mDeep diving: how to explore a new code base
30mFrustration Driven Development
30mCome on in! Making yourself at home in a new codebase
01h 22mBreaking Down the Barrier: Demystifying Contributing to Rails
