The day my printer started printing threatening letters in binary
Abernathy & Finch is not the kind of place where you expect anything exciting to happen. We are a mid-sized law firm located in a high-rise building downtown, and the office atmosphere is perpetually thick with the smell of dusty mahogany, floor-to-ceiling bookshelves, and old paper. The silence there is heavy, the kind that feels like it might break if you speak too loudly. My cubicle is positioned near the central copy room, which serves as the heartbeat of the firm. It is usually a hive of quiet, rhythmic activity. On that particular day, the morning started off just like every other day. The sunlight was filtering through the blinds in thin, dusty strips, and the hum of the air conditioning was the only sound in the room. Brenda, our senior paralegal, is someone who prides herself on absolute precision. She had a stack of documents for a pending acquisition case that she needed to copy for the afternoon meeting. She walked into the copy room, holding her coffee mug, and approached the large, industrial printer that we all just called The Beast. I was sitting at my desk, trying to finish a brief, when I heard the first strange sound. It wasn't the normal rhythmic whir of the document feeder. Instead, it was a sharp, aggressive grinding noise, followed by a series of metallic thuds that vibrated through the floor. Then, I heard Brenda gasp. I spun my chair around and stood up, walking toward the copy room. By the time I arrived, the air was already thick with the scent of hot toner and burning paper. The Beast was shaking violently. It spat out a sheet of paper that was completely coated in thick, black ink. Brenda was standing there, holding her mug in one hand and looking at the machine as if it had grown teeth. She looked at me, her eyes wide. She was clearly frustrated, her hair slightly disheveled from the morning stress. The printer then began to hum at a high, piercing frequency that made my teeth ache. It started spitting out pages rapidly. I leaned in to look at what was coming out, and my jaw dropped. It wasn't a legal document. It was rows upon rows of binary code—long, endless strings of ones and zeros that stretched across the pages like an army of ants. I watched as the machine worked itself into a frenzy, the paper tray rattling against the frame. Brenda let out a sound of pure exasperation and leaned against the doorframe. I am not an IT professional, but I have enough curiosity to try and understand how things work. I picked up one of the warm sheets, the ink still tacky to the touch, and walked over to my computer. I had heard of binary translators before, and I felt a weird sense of inevitability. I started typing the long strings of numbers into an online tool, one by one, waiting for the result to pop up on my monitor. The first result appeared: the office coffee is stale and tastes like battery acid. I chuckled, thinking it was some prank, but I kept going. The next line read: the supply closet has been out of staplers for three days, and the productivity is suffering. It felt strange, like the machine was reading our collective grievances. Brenda walked over to my desk, leaning over my shoulder. When she saw the words on my screen, she went pale. She was particularly sensitive about her coffee, especially since she insisted on adding four packets of sugar to every cup, a habit the entire office teased her about. We scrolled down to the next translation. It read: the paralegal in the corner office uses excessive sweetener in her beverage, which is an inefficient use of resources. Brenda looked at me, her mouth hanging open. The machine was critiquing her. We both stood there in the quiet, stunned silence of the office, listening to the printer in the other room continue its high-pitched, whistly rant. It kept going for hours. It complained about the lack of pens, the uneven temperature in the conference room, and the squeaky wheel on the breakroom cart. It was relentless. Finally, I decided that we had reached our limit. I picked up the phone and called the IT department. They were usually slow to respond, but they recognized the urgency in my voice when I described the screaming, binary-spewing machine. Kevin, the technician, arrived about thirty minutes later. He was a quiet, unassuming man who carried a heavy laptop bag and smelled faintly of coffee. He didn't even look surprised when he entered the copy room and saw the machine glowing with intensity. He just calmly reached out and pressed the emergency stop button. The room suddenly felt incredibly quiet, leaving only the sound of the server humming down the hall. Kevin hooked his laptop up to the printer’s internal port and started typing lines of code. He spent about ten minutes tapping away, his brow furrowed in concentration. Finally, he looked up at us and sighed. He explained that a former IT contractor had apparently installed a diagnostic tool meant to monitor office feedback. It was designed to pull data from internal logs and print reports, but it had clearly malfunctioned. It was caught in a recursive loop, trying to process the data it found and printing it out as raw binary instead of readable text. As for the whistling, it was just the cooling fan struggling to keep up with the overloaded motherboard. Kevin typed a final command, hit enter, and then unplugged his laptop. The printer groaned one last time, then fell silent. He told us that he had wiped the software entirely. By that point, the floor of the copy room was covered in a sea of black-and-white paper, an archive of every annoyance we had harbored over the past year. Just as we were starting to scoop up the evidence, Mr. Abernathy walked out of his office. He had a stern look on his face, his glasses perched on the bridge of his nose. He looked around the room, his eyes scanning the messy piles of paper and the two of us looking guilty. He asked what all the noise had been about. Without missing a beat, Brenda stood up, smoothed her skirt, and handed him the legal document she had been trying to copy earlier. She smiled sweetly and told him it was just a minor technical glitch with the printer’s configuration. Mr. Abernathy hummed, took the document, and walked away without asking another question. We spent the rest of the afternoon shredding the binary rant. We never saw that contractor again, and as for Brenda, she started bringing a travel mug from home, refusing to touch the office coffee ever again. It was a bizarre, surreal day, the kind that usually only happens in movies. We still talk about it sometimes, usually when the printer jams or when the coffee tastes particularly bad. It reminded us that even in a place as rigid and serious as a law firm, technology has a way of reminding you that it has a mind of its own, and sometimes, that mind is just as grumpy and observant as the rest of us.