Why developers should detach from their code @TestDouble
Why developers should detach from their code  @TestDouble
Uploaded December 2025 | Updated September 2026, 2 weeks ago
During a conversation around legacy software application challenges, Interim Principal Consultant Dave Mosher shared why he thinks it's important to have a healthy level of detachment from your 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
Why developers should detach from their codeThe Garmin SDK membership sticker shockWhen software test coverage goes wrongSentiment evaluation with agentic codingSoftware testing strategies: From the outer edges inThe chaos of legacy systemsWere hiring a creative, get stuff done Senior Content ManagerHow to Debug Rails 7 with VS CodeZero downtime Rails upgrades (RailsConf 2023)When a legacy software rewrite makes senseHow to Make a Gem of  a GemEnd-to-end Testing with Cypress Series: 08 DRY Test Setup
Test Double |

Why developers should detach from their code

SHARE TO X SHARE TO REDDIT SHARE TO FACEBOOK WALLPAPER