July 14th, 2024

A prank cursor resulted in an employee being fired before they started (2020)

An intern at Microsoft was fired for a prank involving a middle finger cursor in Windows 3.1. After uproar and management involvement, the intern was rehired, prompting discussions on bug classification and emphasizing the need for rigorous code reviews and quality assurance.

Read original articleLink Icon
A prank cursor resulted in an employee being fired before they started (2020)

An intern at Microsoft was fired before officially starting due to a prank gone wrong. The intern added code to the Windows 3.1 system that changed the index finger cursor to a middle finger under specific conditions. This prank made its way into a beta release distributed to various companies and testers, causing an uproar when the offensive cursor nearly appeared in a magazine screenshot. Senior management got involved, and the responsible individual was initially let go. However, they were later rehired after a brief break, likely following a stern discussion. The incident sparked discussions on bug classification within the company. Despite the controversy, the intern's return suggests a learning opportunity for both the individual and the company's processes. The situation highlighted the importance of thorough code reviews and quality assurance to prevent such incidents in the future.

Link Icon 8 comments
By @fuzzythinker - 9 months
Bad title. As stated in the article, the employee was not fired, he's just an intern that left for 2 weeks before returning as a full-time. PR team reported (truthfully) that the employee is no longer with the company, but the article seems to indicate that company still honored the full employment after.
By @PlunderBunny - 9 months
I almost caused a version of our product to be shipped with a 'Blah' hyperlink on the About window. I was testing a new style of button, and the About window was just a convenient place to put it. This was a long time ago, prior to our adoption of source-control in the company, so I made the builds directly off my laptop. There were many lessons I _should_ have learned, but what I chose to do was to surround all my testing code with #ifdef _DEBUG to make sure it didn't get out to real customers.
By @crtified - 9 months
Funny how it's considered ethically ok to cause a great deal of angst and bother with the bugs and features of corporate releases, provided the problematic elements are entirely couched in 'professional' language and symbology.
By @BlackShade - 9 months
Am I the only one surprised that they still had a job and the position wasn’t retracted? That is the most surprising part of the story to me.
By @hypeatei - 9 months
I'm not a fan of easter eggs in code for this exact reason but c'mon... a slip up like that being rolled out to thousands of customers is hilarious.
By @mifydev - 9 months
You had me in the first half. I thought that during that time "no blame culture" wasn't a thing, especially since Bill Gates's leading style was yelling a lot. Either way, it's great that they kept the employee.
By @willsmith72 - 9 months
Fun anecdote, but do you buy it? An intern can really get this kind of change through approval to a test build? Who are they, Jia Tan?
By @HenryBemis - 9 months
To be fair, if they fired him, they should have fired everyone else in the chain of command that knew about this and left it in the codebase.