Also, I'm quitting tomorrow and you're in charge of MysteryTool maintenance. I'd start by upgrading the .NET version, that baby's still running on Framework 4.5!

[–] [email protected] 23 points 12 hours ago* (last edited 12 hours ago)

Work memory unlocked:

I once was tasked with a metaphorical trip to the basement to fix Cthulhu knows what in the Old Code. Thing was built on top of an ancient CLI tool that consumed and returned SOAP XML. It was terrible.

I spent a month untangling that mess and even pushed a fix to the tool. About a month later I get a phone call from someone asking me if "I was the guy who fixed the tool". I said yes and was immediately offered a job to take over as lead dev on that team. Sensing a trap I politely declined. Dude sighed and basically said not to worry, it would have been miracle to find someone the day before he quits.

Felt like this:

[–] [email protected] 16 points 12 hours ago

Its because the senior Dev doesn't know how it works either. He inherited the project from another team.