re: What's your spookiest coding story? VIEW POST

FULL DISCUSSION
 

Real horror comes when the things are "realistic". So I'll go with this one from one of my previous jobs.

 
 

Many years ago my supervisor at the time was making major changes to dozens of business objects and, of course, tons of unit tests would fail. He solved the problem by commenting out all the unit tests. No time for unit tests because, "the clients don't want to pay for that."

That turned out to be a very costly mistake in the years that followed.

 

For me it was quite different.
My supervisor didn't want to have unit tests, and I wasn't able to change his mind.

So, I created them anyway (just to be sure that my code worked correctly) and I didn't include the project into the solution.

Of course, it turned out that they were useful, especially for a particular algorithm. But of course he didn't recognized the value of the tests, and that he was wrong.

code of conduct - report abuse