Engineer Executes Elaborate Revenge Prank via Disk Formatting Simulation
A former engineering student retaliated against a workplace bully using custom software.
1The Toxic Office Environment
In the late 1990s, an engineering student named Joe worked at an Australian mobile carrier. The messaging lab environment was defined by constant practical jokes, including hidden prawn heads and sabotaged office equipment. One specific colleague, identified as TF, frequently harassed Joe by roaring in his ear to induce sudden fright.
2Planning the Strategic Retaliation
Joe decided to orchestrate a legendary revenge plot during his final week of employment. He leveraged the presence of Borland C compilers on all office workstations to develop his solution. By timing the execution to occur after his departure, Joe ensured he would be safely away when the prank finally triggered.
3Technical Execution of the Prank
Joe wrote a program designed to mimic the visual interface of an MS-DOS disk formatting operation. To increase the realism, the software wrote junk data to a temporary file, causing the PC's disk activity light to blink continuously. This visual feedback successfully convinced the target that their entire drive was being erased.
4Automating the Delayed Trigger
The prank was integrated into the system via the autoexec.bat file, ensuring automatic execution upon every boot. Joe configured the script to remain dormant until approximately one month after his departure date. This delay effectively decoupled the prank from his physical presence, making the source of the code difficult to trace.
5The Moment of Impact
Five or six weeks after Joe left the company, a former colleague contacted him with the results. The program had successfully executed, causing TF significant distress as he believed his data was being destroyed. The prank concluded with a message revealing the ruse, confirming the success of Joe's long-term psychological operation.
6Engineering Ethics and Boundaries
This incident highlights the blurred lines between harmless office camaraderie and targeted workplace harassment. While the prank utilized legitimate programming skills, it functioned as a tool for conflict resolution in a non-professional environment. The lack of formal HR intervention allowed the situation to escalate into a technical act of vengeance.
7Legacy of Workplace Pranks
Workplace culture in the 1990s often tolerated behaviors that would be considered unacceptable in modern corporate settings. The reliance on physical pranks like confetti or hand cream suggests a lack of structured professional conduct. Joe's story serves as a historical example of how technical employees historically navigated interpersonal office conflicts.
8Lessons in Professional Conduct
The outcome demonstrates the risks of fostering a culture where pranks are the primary method of social interaction. While Joe achieved his goal of revenge, such actions carry significant professional risks. Modern workplaces prioritize psychological safety, rendering these types of technical retaliations obsolete and potentially damaging to one's long-term career reputation.