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 articleAn 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.
Related
A Rich Neighbor Named Xerox
In 1983, Steve Jobs confronted Bill Gates over Microsoft potentially copying Macintosh ideas. Despite agreements, Microsoft released Windows, sparking a tense meeting. Apple's lawsuit for copyright infringement failed. The incident reflects the intricate Apple-Microsoft dynamics during early computing.
An arc welder in the datacenter: what could possibly go wrong?
A former IBM engineer fixed a cracked metal frame on a stock exchange's printer in the 1960s. A later inexperienced repair attempt caused chaos, emphasizing the need for expertise in critical system maintenance.
Whose bug is this anyway?? (2012)
Patrick Wyatt shares bug experiences from game development, including issues in StarCraft and Guild Wars. Compiler problems caused bugs, emphasizing the need for consistent tools and work-life balance in development.
Firing Myself
Noormar, a developer, accidentally cleared a production database at a Social Gaming startup, causing revenue losses and customer complaints. The incident led to guilt, a tarnished reputation, and eventual resignation.
Stop installing that software – you may have just died
A tech support incident at an Air Force base during wargames led to a simulated bomb disabling the base, causing work stoppage. The story highlights inefficiencies and challenges in tech support roles.
Related
A Rich Neighbor Named Xerox
In 1983, Steve Jobs confronted Bill Gates over Microsoft potentially copying Macintosh ideas. Despite agreements, Microsoft released Windows, sparking a tense meeting. Apple's lawsuit for copyright infringement failed. The incident reflects the intricate Apple-Microsoft dynamics during early computing.
An arc welder in the datacenter: what could possibly go wrong?
A former IBM engineer fixed a cracked metal frame on a stock exchange's printer in the 1960s. A later inexperienced repair attempt caused chaos, emphasizing the need for expertise in critical system maintenance.
Whose bug is this anyway?? (2012)
Patrick Wyatt shares bug experiences from game development, including issues in StarCraft and Guild Wars. Compiler problems caused bugs, emphasizing the need for consistent tools and work-life balance in development.
Firing Myself
Noormar, a developer, accidentally cleared a production database at a Social Gaming startup, causing revenue losses and customer complaints. The incident led to guilt, a tarnished reputation, and eventual resignation.
Stop installing that software – you may have just died
A tech support incident at an Air Force base during wargames led to a simulated bomb disabling the base, causing work stoppage. The story highlights inefficiencies and challenges in tech support roles.