Twin brothers wipe 96 government databases minutes after being fired

Post by [deleted] » Thu, May 14, 2026, 6:02 AM UTC

joe_mamba wrote: post #217

Twirrim wrote: post #213

Earlier quoted context omitted.

If you're talking about Oracle, the large round previous to that they did had individual meetings with employee, manager, and HR. With so many layoffs it took a week+ to do, effectively torturing an entire set of employees who had no idea if they'd have a job by the end of the hour, let alone week. I'm not sure there's any good way to lay off large amounts of staff (besides not getting yourself into the situation in…

>I'm not sure there's any good way to lay off large amounts of staff Someone on HN once wrote that after the dot.com bust, Yahoo! HR had 1-1 meetings with every single employee that was part of the mass layoffs back then, and they did this for hundreds of workers. Boy what I wouldn't give to go back to such state of affairs, even though I wasn't yet part of the workforce back then. An older family friend of mine who…

Post by rixed » Thu, May 14, 2026, 6:06 AM UTC

gcr wrote: post #266

lazyasciiart wrote: post #199

Earlier quoted context omitted.

Amateurs. My employer does mass layoffs by terminating access to everything except their email account at 3am, and then sending an email to the victim saying “you were let go at 3am”. Managers get to figure out who’s left on their team by pinging everyone when they learn about it at work.

Google powerwashes your corp Chromebook when they let you go. A friend was composing an email on the train when their screen went black and the device reset itself to factory settings. They even send the “you’re being fired” email to their personal email they have on file. Didn’t even schedule a meeting.

Post by rixed » Thu, May 14, 2026, 6:15 AM UTC

tempaccount5050 wrote: post #45

scottlamb wrote: post #39

> [Opexus] said that “the individuals responsible for hiring the twins are no longer employed by Opexus.” Getting close to the classic Monty Python line: "Those responsible for sacking the people who have just been sacked, have been sacked." Jokes aside, stuff like this sucks because I suspect many employers will take from it the most extreme, dehumanizing lessons, e.g.: (a) make firings [edit: including lay-offs] as…

When you are talking about access like they had "make firings as abrupt as possible including terminating all access immediately" not doing this is incompetence. This is absolutely a standard and has to be for these kinds of positions. I've never worked anywhere where it wasn't for the majority of IT staff. You meet with HR, someone clears your desk, and security walks you out.

Post by pretzel5297 » Thu, May 14, 2026, 6:21 AM UTC

soVeryTired wrote: post #44

> On March 12, 2025, a search warrant was executed at Sohaib’s home in Alexandria. Agents grabbed plenty of tech gear but also turned up seven firearms and 370 rounds of .30 caliber ammunition. Given his former crimes, Sohaib should have had none of this. For god's sake, don't commit crimes while you're committing crimes.

Post by odysseus » Thu, May 14, 2026, 6:22 AM UTC

zeafoamrun wrote: post #279

yaur wrote: post #156

Earlier quoted context omitted.

Terminating access and rotating passwords (if needed) while the person is in the meeting but has not yet found out they are being let go has been SOP for at least the last 20 years

Heh, a place where I worked some guy who left kept committing code for months (he went to work for a company we were a vendor for). Some of my teammates knew and just thought it was no big deal, he was fixing bugs and adding features. The color the director turned when he found out!! Oh man.