"Understood as senior: Legacy code that I wrote myself is hard to read." Your comment came at the perfect time. I just finished debugging a "high urgency" prob

"Understood as senior: Legacy code that I wrote myself is hard to read." Your comment came at the perfect time. I just finished debugging a "high urgency" problem with a program I developed and maintained for the past 10 years. The program started simple with a small list of rules to apply against data sets. Over time the list became a tree of rules that expanded in both breadth and depth. It was refactored once to get the design in line with the rules of the time. The "high urgency" issue turned out to be the program working correctly. But, the functional user wasn't able to keep in mind some of the rules he set. It took me a half hour, with lots of "why did I do that", to explain it again to the user.