So he was pissed because they gave him less work to do???
I’m trying to understand it
IT work is feast or famine.
“IT people, your not doing anything, what the hell do we pay you for?”
“IT people, everything is on fire, what the hell do we pay you for?”
How is that feast or famine
I think they mean in terms of workload, not like pay or something. Either you have a lot of work, or very little work. But when you’re needed, you’re needed urgently.
i goes it is ON not OR
your honor, I would move to dismiss on grounds that my clients actions were based as fuck.
I’d argue that he gave them extra code, a bonus if you will.
and unlike dennis nedry, he didn’t have to get killed by a dinosaur to do it.
I developed a spreadsheet for a company I worked for a few jobs ago. When I left I used a picture of Dennis to lock everyone out of the spreadsheet but only for one day, months after I left. Stupid idea, but felt good.
Edit: this was it:
I had created a few things on Google sheets that my coworkers were using. It wasn’t anything groundbreaking, but one was a spreadsheet I’d made that had all of our driver’s availability to assist with scheduling. The sheets were on my personal account, and we didn’t end on good terms, so I just locked them all out. It was funny getting all the texts asking for access the next day. I told them to make their own.
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.
Same for my last job. My bosses and managers harassed and insulted me. They said I was useless and stupid.
I quit with 3 months of “notice” (standard in France to help you find a new job). They didn’t care during those 3 months. In the last week they panicked because they could not find a replacement that did everything I fixed every day.
I also interviewed my replacement, a junior out of school with big diplomas. When I asked if he knew Linux, he said “not really.” I thought “they are fucked with this guy.” They wanted to hire him because he was the son of some guy. I said to my boss that he would be a perfect fit for the company.
Unknowingly I was the kill switch. I sent them one last email with all the information they needed and told them to go fuck themselves in a polite way.
malicious compliance, I like it
but even if you weren’t caught, it’s not worth it to personally be bitter like that.
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.
comment it with some bullshit about avoiding race conditions
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.
Talk about incentivizing us to make even more impactful kill switches!
For the last time, I didn’t leave a kill switch – I just refused to document anything!
You are truly a madman
Edit: or a madlady
M’lady
Why do kill switches when you can just hog all the work of maintaining some critical part of the infrastructure and make it’s functioning and maintenance so opaque and impenetrable that the employer can’t replace or fire you without their shit catching fire soon after. It doesn’t have to be malicious or illegal.
His efforts to sabotage their network began that year, and by the next year, he had planted different forms of malicious code, creating “infinite loops” that deleted coworker profile files, preventing legitimate logins and causing system crashes
I wish this guy was were actually politically motivated, but he seems to have been just really petty minded person.
Why do kill switches when you can just hog all the work of maintaining some critical part of the infrastructure and make it’s functioning and maintenance so opaque and impenetrable that the employer can’t replace or fire you without their shit catching fire soon after.
This is literally my firm’s core business practice. We’ve been at it for so long that at this point we have to be included in competing bids because we are the only ones in the world that can do certain specific things.
That’s what my old company used to do. You did this? Do a KT to some underpaid remote employee and when they leave it’s again your responsibility to maintain it, alongside the new bugs and spaghetti they introduced.
We once told a SP50 customer that we would not provide a business critical service because an employee went on sabatical for a month and she had the only working version on her cookery computer. At that point the customer was so integrated with us that it would take them years to replace us.
so opaque and impenetrable that the employer can’t replace or fire you without their shit catching fire soon after.
Somehow, that’s the kinda roles I always land in lol
Initially makes me wonder how the employer could be so dumb as to give one employee so much access. But then I remember a former employer of mine did the same and worse.
Colleague was known for writing his comments in such a way that only he could read them, including mixing in German (US based company doing all business in English). He was also the admin of our CAD system and would use it as leverage to get his way on things, including not giving even default user access to engineers he didn’t like. We migrated systems and everyone was thinking, “this is it, the chance to root this guy out of the admin position” and… they gave him admin access again. Not even our IT department had the access he had. I left before the guy retired / was fired, this post is making me wonder if he left peacefully or left bricking the CAD system out.
My previous work didn’t revoked my access to their CMS. I was so upset when they laid me off after telling them my wife is pregnant.
But I ain’t that stupid.
Aren’t you no longer binded by profesional silence? Just log in into their DB, export it and try to get a seller
Again, not that stupid.
Initially makes me wonder how the employer could be so dumb as to give one employee so much access.
Right now, just based purely on the access I need to do my day-to-day job involves me having access where I can pretty much nuke everything from orbit, with an ssh loop.
At some point, you need to trust your employees, in order to get work done. Sure, you can lock it all down tightly, but then you just made work take longer. It’s a trade off.
Initially makes me wonder how the employer could be so dumb as to give one employee so much access.
The amount of access he had doesn’t surprise me. He’d been there for 11 years already likely working on many things as he interacted with systems in the course of his legitimate work. While its possible to set up access and permissions in an organization utilizing the “least privilege principle”, its expensive, difficult to maintain, and adds lots of slowdowns in velocity to business operations. Its worth it to prevent this exact case from the article, but lots of companies don’t have the patience or can’t afford it.
We’ve all considered it
Oh yeah, but the thing that usually offsets the intrusive thoughts is a lot of courts treat this as the crime of “hurting rich people” which comes with like 30 years in pound you in the ass penitentiary.
Oh. Personally for me it’s code reviews that prevent me from doing it, but pound you in the ass penitentiary is a good motivation too
The secret is get promoted to where you do the code reviews. Then just get too busy to do them reliably. Timebomb activated.
A 55-year-old software developer
… and…
Lu had worked at Eaton Corp. for about 11 years when he apparently became disgruntled by a corporate “realignment” in 2018 that “reduced his responsibilities,” the DOJ said.
So he was 48 at the time he started this. Was he planning on retiring from all work at 48? I can’t imagine any other employer would want to touch him with a 10ft (3.048 meters) pole after he actively sabotaged his prior employer’s codebase causing global outages.
I’m sure DOGE is actively considering hiring him.
He fucked up. But it’s also kinda funny.
guy really tagged his name on the kill function, which was running on his own system. smh my head
And now imagine doing this or sort of this destruction in a smaller company that has one to three mediocre admins at highest. One can kill this company and they would never get it why the computers got weird.
Reminds me of the timebombs in windows 2000. I guess he’s forced to start fresh.
Timebombs in Windows 2000?
Timebombs in windows 2000!
Oh shit that is a large number
out of the loop :
2000 x 1999 x 1998 x … x 3 x2 x 1 = 2000 !
