Code you dont touch doesnt really break—what happens when you touch it? @TestDouble
Code you dont touch doesnt really break—what happens when you touch it? @TestDouble
Uploaded March 2026 | Updated September 2026, 2 weeks ago
Staff Consultant Steve Jackson breaks down the danger in code you don't ever really touch, and why it's important to think about ripple effects. This can compound when you're working within a complex legacy software application.
Code you dont touch doesnt really break—what happens when you touch it?Parcel a First Look at Creating Your Production BuildRuby Kaigi 2023 - Aaron Patterson InterviewWhy taste and judgment is important in agentic codingPlease dont mock me (Justin Searls)How to Scratch an Itch (Justin Searls)Surgical Refactors (Justin Searls)When developer tickets become history booksWhy developers should detach from their codeThe Garmin SDK membership sticker shockWhen software test coverage goes wrongSentiment evaluation with agentic coding
Test Double |

Code you don't touch doesn't really break—what happens when you touch it?

SHARE TO X SHARE TO REDDIT SHARE TO FACEBOOK WALLPAPER