Monday, May 30, 2022

Fuckbot 2000

The cocky new hire made the mistake of crossing paths with the smartest guy in the IT department. I don’t usually like tooting my own horn, but it’s difficult to resist taking matters into your own hand when a hot young newbie tries to upstage a hard-working employee by doing “favors” for management. Especially when you’ve dealt with the exact same make and model of androids in the past.

All it takes is one carefully crafted phone call with a precise series of tones to trigger a bug that freezes the robot in place. Hey, it’s not my fault the company hasn’t rolled out patches to their products. Or maybe they figured some people actually have a thing for controlling their machines this way. People like me.

It was too late for him when he rebooted in my basement computer lab as I had already disabled all his motor and emergency systems. A few buffer overflows here, a segmentation fault there (did I mention I have a thing for erratic twitching caused by system errors?) and I had full access to his programming. Of course, I was careful not to change too much lest it arouse suspicion. Just made him a little nicer and a bit more forthcoming with me about what our bosses disclose to him. In the office, it’s like nothing happened. But at night when I send him a secret code, he comes over and becomes my personal Fuckbot 2000, ready to go back to work and impress the suits the next day after hours of intense sex. The perks of being a robot fetishist geek.

No comments:

Post a Comment