Oh, god. I have something similar. I'm withholding names and won't go into specifics to protect the innocent.
At a previous job, I'd been telling the boss for years something he wanted automated couldn't be automated, unless he hired somebody to maintain the automation code, pretty much as a full-time job. Basically, the process being automated was a moving target.
So one day he decided to go ahead anyway and wrote the code over a weekend. It only worked for a week. And yes, somebody had to maintain his code all the time from that point forward.
Although the available choices could be scary, they are not really terrifying.
For bone chilling scares, I would point to decisions made to update old, large (1 million LOC and up), MFC based projects. Here are a couple of samples off the top of my head:
- We need a 64-bit version of the application(s).
- We want to introduce the application on the Chinese market, so let's add Chinese UI.
- Let's change the projects from Multi-Byte to Unicode Character Set.
"When you don't know what you're doing it's best to do it quickly" - Jase #DuckDynasty
Multi-Byte Vs Unicode; why on earth was it not dealt with the day after it was discovered that there are people outside of Europe and USA. Windows should have been 100% unicode every since it no longer depends on MS-DOS.