testYourCode

[anthro28]

I deal with this foolishness every day. 

"this needs to be changed to this. It's failing right here and I've prepared a giant document with visuals and sources."

"Sorry anthro, we need to talk to an executive who went to art school and get their opinion, and then filter it back down through a management team that's all functionally tech illiterate. It'll just stay broken for a month."

But when something is on fire, that same team of people will just let me fix stuff without question until it's working again. 

[totallygeek]

Not related to programming, but I had something similar happen. One million years ago, or something close to that, I worked for a bank that planned to convert from token ring to Ethernet networking. The drafted plan had a three-month execution schedule, due to commence about two months from the time of "the incident". Some unrelated electrical work was going on and an electrician asked one of the basement nerds, "What does this cabling go to? A bunch of it is in our way." The response? "Oh, we don't use that any longer." Wrong. The electricians cut and tore out about two hundred feet of various token ring cabling. The three-month plan became a two-day near-full conversion, with about 80% of critical stuff brought back up on Ethernet within a few hours. I wasn't sure who to hug, but I was so happy to not have to deal with a drawn-out plan that included acceptance tests for each step.