Nice!
Comment on Self sacrifice is honorable
glitch1985@lemmy.world 1 day agoDeadman switch. Hit the button before all meetings and if you aren’t back in 2 hours to disable it then it would execute.
melsaskca@lemmy.ca 1 day ago
Comment on Self sacrifice is honorable
glitch1985@lemmy.world 1 day agoDeadman switch. Hit the button before all meetings and if you aren’t back in 2 hours to disable it then it would execute.
Nice!
axx@slrpnk.net 1 day ago
Run it on a separate machine / account. In big corporate environments, your user account could be disabled by the time you walk into the meeting room.
Better solution, if you can, work for open source companies: at least the codebase is already public!
zod000@lemmy.dbzer0.com 1 day ago
If you’re in a position to have access make this sort of thing, you likely have access to code bases or system accounts. This is a good way to go to prison IMO.
veniasilente@lemmy.dbzer0.com 1 hour ago
The trick is to not have to actively do anything, but rather take advantage that employment termination means you legally can not actively do things. A case I recall from a friend was a coworker of his who simply happened to be the only one to know how a particular critical system operated, because the rest of the staff never bothered reading the documentation for emergency. He was not paid for his overtimes for long enough and when he eventually stopped taking overtimes, they fired him for some AI-grade hallucination like “lack of commitment”. Four days after he was fired, they tried to order him to come back for an emergency like he owed them that maintenamce. Though cookie, the company and he signed an employment termination agreement to both their satisfactions that he has no legal obligation to the company.
From what I recall, the recovery procedure was three lines over a telnet connection. No one could even bother to open one (1) tab with the doc and type “HyperTerminal” in the Windows menu, lol.
zod000@lemmy.dbzer0.com 52 minutes ago
Oh that trick I fully employed. They had to retire 19 internal applications within a year of me leaving :D
Schadrach@lemmy.sdf.org 2 hours ago
I actually used to know a guy who pulled this sort of thing. Got 4 years, $100k fine and $428k in damages owed. Caused a huge number of problems for an energy company for a month because he got wind they were going to fire him.
I prefer my version of it, which is knowing both who to contact at our largest customers. I’m under no contract that prevents me from showing a customer where and how the metaphorical bodies are buried were I to be terminated. I could do the other kind of stuff, trivially even, but that’s likely to end in prison…
zod000@lemmy.dbzer0.com 2 hours ago
I’ve been in these sorts of situations (had enormous access to critical systems and data and was poorly treated by employer), but logically I just don’t think it is worth the risk to myself, my family, and my future in general to get revenge on these sort of things. It would need to be some sort of Princess Bride situation (“You killed my father, now prepare to die”) kind of thing to bring me to that sort of insanity.
I have also had coworkers that did similar-ish things and they were quite lucky that all that happened was that they were immediately fired and blackballed.
BarneyPiccolo@lemmings.world 1 day ago
Better, plant it on the account if that co-worker you hate, and still works there, operated off a remote. Then he gets the blame.
MajorasTerribleFate@lemmy.zip 22 hours ago
There it is, that’s the solution.