5 Cognitive Distortions When Touching Legacy Code — CBT for Developers

#cbt #mentalhealth #refactoring #productivity

The Legacy Code Trap

You have been told not to touch it. The comment says "do not refactor this, it is fragile." The tests do not exist. The original author left three years ago. And now you need to fix a bug in it.

Legacy code anxiety is the paralysis that hits when you are staring at 2000 lines of undocumented, untested code. It is not about skill — it is about catastrophic thinking about breaking something you do not understand.

The irony: The more you avoid touching it, the scarier it becomes.

5 Legacy Code Distortions

1. The "Do Not Touch" Fallacy

Thought: "If I touch it, I will break something."
Reframe: "Tests and gradual changes equal safe exploration."

2. Catastrophic Breakage

Thought: "The whole system will collapse."
Reframe: "Start with characterization tests, then refactor."

3. "I Am Not Smart Enough"

Thought: "The original author understood this. I do not."
Reframe: "Understanding is a process, not a fixed state."

4. The "It Works" Trap

Thought: "It works in production. Do not risk it."
Reframe: "Technical debt is a risk too. Make it safer to change."

5. "I Should Rewrite It"

Thought: "Just rewrite from scratch."
Reframe: "Small, safe refractions first. Big rewrites are a last resort."

The 5-Minute Reframe

Notice: "I am feeling frozen about this legacy module."
Identify: "This is the Do Not Touch Fallacy plus Catastrophic Breakage."
Evidence: "Have I written characterization tests? Read the code carefully?"
Reframe: "Tests are my safety net. Start with one small test."
Action: Write ONE characterization test for current behavior.

DEV Community