
Biggest refactoring mistakes and communication

Refactoring at Scale Done Right 🏗️ — with Maude Lemaire
Topic 8 of 9
Published Jul 24, 2025 · Clip 49:07–58:01 (8:54)
Maude identifies lack of communication as the biggest refactoring mistake: changes should be invisible to users and interfaces, yet everyone must know they're happening, because something will inevitably break and on-call engineers need to rule the migration in or out quickly. She recounts her own failure migrating Slack channel-membership data from three tables into one: she didn't yell loud enough, broke group DM-to-private-channel conversion for days with no unit tests covering it, and the debugging engineer discovered the change only via git blame. Good tracing (shoutout to Charity Majors/Honeycomb) eases this, and teams 'shielded' from a migration must never be surprised by incidents.