Rigorous Dev Courageously Lied About Exec's NSFW Printouts And Survived Long Enough To Quit With Dignity

© Provided by the registry

Log files don't lie, and a bad event in this case indicates a deeper malfunction

Who am I? I am waiting? Yes? is it really monday Fear not, dear reader, for Uncle Reg is here with someone else, me? Stories from readers who had a worse day than yours. Enjoy the joy...

Meet the developer we'll call "Ron" who was selected to join the family business this week. We call him Jeremy, the CFO of a recruiting firm who looks like a playboy but is basically a good candidate.

For the most part, Ron found acceptable employment at the company. The technology may be a bit dated, but everything worked and the people seemed genuine. However, Ron couldn't help but think that something was wrong.

Ron worked downstairs with a female-dominated team managing the accounting system. The company's main printing house was also located in their nest. Executives and sales staff had their own printers in the penthouse upstairs. Of course, everything was networked, and a Unix-based printing system took care of who printed what.

One day, one of the women in the office shyly walked into Ron's room, avoiding eye contact. "Something's wrong with the printer," he said, dropping a stack of pages before quickly backing away. Ron said he would look into it and looked at the pages.

Oh my love heavy evil. Many.

Of course, it would be easy to find out who printed it. Ron thought someone was about to have a very awkward conversation.

Then he finds out that the person who ordered the printing is Jeremy, the financial director. Turns out Ron was about to have an awkward conversation.

Without thinking about what to say, he hung up on the intercom. Jeremy angrily demanded that she go to the C-suite immediately. Confused, Ron tossed the offending leaflets (in more ways than one) into the drawer and went upstairs.

Jeremy was upset because his tampon wasn't working. He printed some "important documents", but they did not appear. He wanted to know what happened. NOW:

As he played, Ron checked the print date. In fact, the CFO printed some documents. Of course, instead of printing them on his behalf, he sent them to the main printing house downstairs. If only Jeremy knew what he was doing, all of this could have been avoided and much less embarrassing. They did not manage with the resources of the company.

Ron tells him that the print job was accidentally sent to the main printer queue, but accidentally deleted. Maybe try again with the correct printer.

Jeremy is furious and accuses Ron of lying to him (which he was) and saying he stole the prints (which he was, but what choice did he have?).

After this incident, Ron began to plan his escape. He updated some systems, trained a replacement, then left. In fact, a few months later, he discovered that the company was wanted for various financial crimes, including money laundering and embezzlement.

Have you ever been in a tight spot and had to improvise? Tell us about it by emailing Who, Me. We will present your brave deeds in full.

one night