3 Stages to evaluate code @TestDouble
3 Stages to evaluate code  @TestDouble
Uploaded November 2025 | Updated November 2026, 3 hours ago
Staff Consultant Brian Hughes shares a useful framework to think about evaluating your legacy codebase.

This was part of a wider-ranging conversation on legacy modernization. Check out the playlist here for additional clips from the conversation, plus seminal Test Double legacy talks and helpful screencasts: youtube.com/playlist?list=PL-NoIr_UR3KX8X-ZSZ7OeKkx9Co3HhOce&si=orgumxvnNAh2miqr
3 Stages to evaluate codeSometimes a Controller is just a Controller (Justin Searls)How to tell if AI threatens your jobThe Social Coding Contract (Justin Searls)Diagnosing vibe coding with code smells: superpower or illusion?Unpopular opinions on vibe coding from senior developersThe Tale of the Hidden Consultant: a scary software storyLegacy modernization: What happens when seams are at cross purposes?Ratcheting to zero: How incremental constraints eliminate technical debtDiagnosing vibe coding with code smells: superpower or illusion?The Rails of JavaScript wont be a Framework (Justin Searls)Why AI is not good at testing
Test Double |

3 Stages to evaluate code

SHARE TO X SHARE TO REDDIT SHARE TO FACEBOOK WALLPAPER