Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
@MisterArie no he didn't use sudo for 4 days. I'm surprised actually that he didn't need sudo for that long.
-
If I was your boss, I'd got mad on you, not him.
He made a mistake, of course, but he did it at work. Would have been different if he left a machine with secret content unlocked in the middle of an airport.
But still, you managed to fuck up his system and made him lose time, and since time = money....
Nice prank tho! -
@taglia lol, the bosses were in on it too. One wrote in a terminal "I hope no one messes your computer up to badly"
-
@taglia wut there are bosses that get mad at pranks?
Ive once put on https://fakeupdate.net on a colleagues pc. At a certain time I asked him how far the update was, he replied "108%" without noticing xD -
Excellent prank! I tip my hat to you.
It's all very well saying that you kept him away from work for 4 days until some malicious person walks into the office and finds an unlocked PC to bring chaos to the system.
My db sits logged in to live with insert and update privileges there for the taking, so when I step away from it for more than 5 seconds I lock that shit up. I expect other devs to take the same responsibility.
Shame on them if they think a little prank is worse than teaching someone a valuable lesson. -
@zemaitis ... I would say quit your job if you cant do little pranks. Non stop working is less productive then some small pranks in between...
Another prank (the oldest in the books) you could try: put a post-it under your colleagues mouse sensor. Let them figure that out xD -
@Codex404 now go back to first post and notice that the guy spend DAYS in fixing this prank, it was not a small prank. Lets keep facts straight
-
@zemaitis he could work without using sudo for 4 days, on the fourth he found out he didnt have rights.
-
@diegovincent We have another account that is technically available to use for all IT people. It is an admin account that he could have used to fix what I had done. In fact, it was with the same account that I had pranked him with.
In a few words, it's a backdoor that anyone can use to access each other's accounts...
Not very safe (I know), but leave it to management to accept it as the status quo. -
@zemaitis I agree.. Pranks ruining work shouldnt be left alone.. If something terribly goes wrong, pranker will run away. Mental agony is too underrated..
-
@Codex404 stop generalizing and pushing your opinion on others
-
@zemaitis Im just stating facts? I haven't given any opinion about it in my last comment.
-
@zemaitis And since you probably want some proof of my so called facts there have been many researches on the topic and one of them can be found here: https://cio.com/article/3019110/...
Well, that’s one way to stop someone from harassing you online. But damn....
Who. The. Fuck. Did. This.
This one time I aliased a coworkers 'sudo' with 'sl' (sl shows a train running across the screen)
And then I removed him from the sudoers group and sudoers list.
I then magnified his screen 200%
Changed his background to a shitty narwhal.
And then full screened a terminal with the 'sl' train stuck in a while loop.
You can't control c out of the terminal.
He solved the first part really quickly, fixing the full screened terminal and exiting out of it, magnification and the background.
But took him 4 days to find that I had fucked up his sudo. Apparently, he didn't need to use sudo in those 4days. It wasn't until he mentioned it out of the blue.
How did he find out about it? He was running an important script that had sudo in it. When he ran the script a train would pop up and his script would terminate early.
He came to me and cursed me to Satan's anus. He then asked me to fix it, but then changed his mind and said that he'd do it himself. After a while he couldn't figure out what I had done.
I walked him through it. Told him that he had to go to his .bashrc file and remove the alias.
Later he comes back to me and curses me to the 12th circle of hell. He found that he was no longer a sudoer. At this point he gave me access to his computer and told me to reverse everything that I had done.
Added him back into the sudoers group and called it a day.
Lesson to be learned? Don't leave your machine unlocked.
rant
asshole coworker
i'm the asshole
prank