Lol everyone probably fantasizes about such thing sometimes, but even if you weren’t caught, it’s not worth it to personally be bitter like that.
Just got laid off and could had done the same. Except I don’t have to.
Internal systems are so bad and undocumented and I was like only IT specialist there who could use linux, and so many things related to core businesses were just basically behind me.
The kill switch has made it self.
Funny how I would have written more documentation if I ever was given the time.
But don’t be stupid about it. Stash a date somewhere that you manually update every so often (so that it’ll stop being updated if you’re fired) and then add a bunch of random waits whose durations scale with the time since that date. If you’re worried that the code will be found, comment it with some bullshit about avoiding race conditions.
…and now I can’t use that idea, since this comment would be used in court. If I did it to a weapons manufacturer, they’d probably get the death penalty somehow.
Fair but I wouldn’t ever work for weapons manufacturing.
Also sabotage in that context would have heavy punishment, and at worst could cause collateral damage.
I was using that as an example because it was the worst thing that came to mind. There is a whole gradient between non-profit and weapons manufacturer.
I didn’t plant anything and I could still brick the production backends of a former employer because some poor ass decisions were made when choosing technologies and then when I pointed it out that it’s pretty bad the technology was stuck with so literally all it takes is sending 2-3 requests so all pods die.
Lol everyone probably fantasizes about such thing sometimes, but even if you weren’t caught, it’s not worth it to personally be bitter like that.
Just got laid off and could had done the same. Except I don’t have to. Internal systems are so bad and undocumented and I was like only IT specialist there who could use linux, and so many things related to core businesses were just basically behind me.
The kill switch has made it self. Funny how I would have written more documentation if I ever was given the time.
Really depends on what you do for a living… Non-profit? Sure. Weapons manufacturer? Fucking have at it.
But don’t be stupid about it. Stash a date somewhere that you manually update every so often (so that it’ll stop being updated if you’re fired) and then add a bunch of random waits whose durations scale with the time since that date. If you’re worried that the code will be found, comment it with some bullshit about avoiding race conditions.
…and now I can’t use that idea, since this comment would be used in court. If I did it to a weapons manufacturer, they’d probably get the death penalty somehow.
Lmao, amazing
Fair but I wouldn’t ever work for weapons manufacturing. Also sabotage in that context would have heavy punishment, and at worst could cause collateral damage.
I was using that as an example because it was the worst thing that came to mind. There is a whole gradient between non-profit and weapons manufacturer.
I didn’t plant anything and I could still brick the production backends of a former employer because some poor ass decisions were made when choosing technologies and then when I pointed it out that it’s pretty bad the technology was stuck with so literally all it takes is sending 2-3 requests so all pods die.
But why do it.
Similar cases with my old company. In my case people who would had suffered the most direct consequences would had been my colleagues who I respect.
But I could totally cause trouble without any backdoor access.