It's a busy time at this big software vendor when a must-fix bug report comes in on a legacy product, reports a pilot fish on the inside.

"Our system was very stable and we were making great strides at adding functionality to our new product," fish says. "No one wanted to take the time to go back and fix an old problem.

"The issue was not actually coding the fix, but following the old release process. That was going to be very time consuming.

"After many efforts, we couldn't convince management that the issue should be closed with no plans to fix.

"Two developers were identified as candidates to fix the problem. The first was the former owner of the code, and the other was the tech lead. Both knew the system and the old release processes. Each gave good arguments on why the other person should perform the work.

To read this article in full, please click here