upvote
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.

reply
Was his name … Milton?
reply
"We fixed the glitch"
reply
I have door codes and passwords for a major organisation that I last worked for somewhere in the region of 20 years ago. They haven't rotated a damn thing. I still know people who work there, and I guess technically I still support things for them in an informal question-over-a-pint kind of way, but damn me, put in some effort guys.
reply
This story deserves a movie, or at least a long video essay!

Haven’t laughed this hard in a long time.

reply
You might enjoy this story then. 2 guys at apple continue to finish and ship their product after being laid off ..

https://www.pacifict.com/story/

reply
IIRC 50 Shades had a case of "remember me, the woman you fired? I talked to your boss' boss and I'm your boss now"
reply
so he was doing free labor for your company? What's he getting out of that?
reply
he went to work for a company we were a vendor for

Sounds like he's getting paid to work on the same thing by a slightly different stakeholder.

I'd happily pay $$$$$$ to hire someone with commit access to Cloudflare, AWS or Google's codebase who could fix the goddamn bugs, let alone add new features.

reply
> Sounds like he's getting paid to work on the same thing by a slightly different stakeholder.

This honestly sounds like the sort of thing I'd sit down with the employee, their new employer, and various "Compliance Team" members, and firm up a bit.

Sounds good for everyone.

We get our bugs fixed, $vendor gets to say "Well we have this thing that was developed in-house for BoshNet, that might solve your problem too, it's going to cost you <some comical amount>", and everyone's happy.

reply
No company with a legal rep is going to be happy with that situation - ever.

Who even owns the code the person is working on? Who is responsible when it goes wrong?

reply
Never happy is a bit of an exaggeration. SYSV UNIX had all of these risks and various legal departments went through them as they do regularly for more typical types of research.
reply
When it was explicit, and part of the relationship, sure. Because those questions aren’t questions.
reply
Which is why I said you'd sit everyone down and thrash it out.
reply
That’s the “firming up” bit. You have a contract that deems the code “work for hire” even though the money flow is wonky. Legally the guy is like any 1099.
reply
reply
> We wanted to release a Windows version as part of Windows 98, but sadly, Microsoft has effective building security.
reply
Just finished reading, love these kind of stories. Thanks for sharing
reply
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.
reply
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.

reply
Most of the employer behaviour described in such gleeful terms here would be outright illegal in most of Europe and open up the employer to risk of being sued for wrongful dismissal, etc.
reply
Skeptical that this would actually be illegal in Europe if all the details were provided.

I went through a similar thing at Amazon. Locked out of my laptop at 3 a.m. and emailed I was laid off. The key thing though is that my official end date was 90 days in the future. Legally, the 3 a.m. lock out was actually just a warning of impending layoffs. I got paid to “work from home” for 3 months after I returned my badge and laptop.

My understanding is that Europe may have longer wait periods, but most tech companies still essentially do the same thing there. Amazon’s laid off Berlin employees still get locked out at 3am and told to do nothing for months while legal does whatever it needs to do to get rid of them.

reply
Funnily enough it is actually illegal in Europe and so our laid off German employees were reinstated by court order, several other countries as well. Amazon presumably ran into the same problem, or was smart enough to know they would: they give plenty of notice to European employees and follow local laws. https://www.reddit.com/r/cscareerquestionsEU/comments/1qpni5...
reply
This is why the EU continues to get much more poor compared to the USA. Turns out "live to work" really does beat "work to live".
reply
Seems like only a few thousand people in the US are really getting rich from this.
reply
Eh, there are ways around that. I've worked for multiple Finnish companies that do layoffs via "lomautus" whereby they put the laid-off employees on a forced, unpaid, indefinite leave. After multiple months of not receiving a paycheck, the employees inevitably "resign".
reply
In Germany that's forbidden, you'd have to pay them.

But you can be placed in a room/office with no windows (not the OS), a computer without internet access and nothing to do. How long can you go on like that?

The law, sadly, can't forbid asshole employers.

reply
Royal Bank of Scotland did that to me and a few colleagues when they didn’t want to pay redundancy whilst closing the only building for us to work in.

Was a battle of wills and eventually after 5 weeks of coming into a random branch office and sitting in an empty room, we came in one Friday to be told that the manager in charge of the building closure had been removed from the project and they would be paying full redundancy pay and we didn’t have to come back in but they’d pay for the next 3 months as well.

Fun as a 21 year old.

reply
And then US tech has the arrogance of claiming "we don't need unions".

yeah, shit like what we're reading here is precisely why y'all need unions.

reply
We’re talking about a Google employee that makes 5x or more of what a European counterpart would. Lack of termination notice and other at will employment is easy to plan for when you make so much money.

Until someone starts providing examples of software companies where the employees are unioned and clear $400k+ annum, the bar is still “no unions”.

reply
Why not fire people humanely, even if you pay a lot?
reply
A full email? We need a "you've been fired" emoji.
reply
U+1FAF5 U+1F525
reply
Man, that's cold.
reply
I think at least on windows you can powercycle it quickly a few times until it gives up this behavior. Not sure about Chromebooks.
reply
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 the first place where you have to)

reply
>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 started working in tech around 2003-2005, told me "back in my day, to get a job, you'd just send your CV to HR@corpo.com, and in 2-3 days you'd get a call asking you when you're free to come over for an interview". Now today you're lucky you get an automated reply back from 50 CVs sent, just for the opportunity to do an impersonal take home assessment as part of the seven stage interview process. It's like screaming into the void of AI bots and automated CV screening systems, while you spin the barrel of the revolver to play the next round of Russian roulette.

And the crazy part is, that when people talk about "the good old days", we're talking about events from recent history, just 10-25 years ago, that a lot of current workers experienced in their lifetime, not stuff from when boomers were kids.

The massive sudden shift in the commoditization of human workers and turning them into faceless labor resources that can be inhumanely disposed of with a keystroke, is real and noticeable to everyone, that I'm envious for you guys who are set to retire soon out of this shitshow.

What comes after this? Have we reached rock bottom, or will it get even worse?

reply
Either your dates or experiences are off, because I've been working in software since 1999 and the easiest time to get a job was quite recent, in the back-half of COVID. The early 2000's were decent, but I didn't experience - or know anyone who did - any sort of "free jobs' period. Also pay was relatively decent but much less than what you saw even 5 years ago. It's only the in the past year or so that the world has appeared to be ending for developers, and I think that pronouncement is premature.
reply
>Also pay was relatively decent but much less than what you saw even 5 years ago.

IDK, I'm not from the US/Bay-Area, nor does my country have any big-tech/FANG jobs to distort the market for what constitutes a "high wage" in tech, it's all the same.

>in the back-half of COVID.

Sure, but Covid was only a short blip, a temporary exception, not a baseline norm for wage/job growth, like the years prior which was a longer period of getting a job was easy, like 2012-2020.

For me where I live now, the career depression I saw came in 2023 already when jobs become less abundant and harder to get, and it only got worse later when mass layoff started. So we're already 3 years in the decline, longer than the Covid boom lasted and things aren't going better yet.

I entered the workforce in around 2012-2014 and it was significantly easier to get a callback from sending a resume than it is now where it's mostly automated rejections. When I say "easy" I also mean you didn't need 7 stages of interviews to get a job back then, you'd have 2 stages and those were pretty chill and get a call back from every 2-3 resumes sent. Now you need to send dozens. I guess "easy" is relative.

>Also pay was relatively decent but much less than what you saw even 5 years ago.

Inflation also happened in that time.

reply
[flagged]
reply
I know enough people who tried, to be able to tell you that it's not all roses over there. Some had to go back to being a corporate slave and some just continue grinding a barely viable business earning much less than they could at a large company
reply
deleted
reply
most businesses are useless scams, few make it big, most people just barely make-by
reply
>You should have tried to create a business or fulfill G-ds hopes for you when you had the chance

Says who? What does God have to do with this topic? And why are you censoring the word God?

>but you sold out and took the easy pay check.

I didn't sell anything, nor was the paycheck easy, it was all hard honest work from school to university to put food on the table for my family. Why do I need to justify myself to you?

>Now You’re fucked

I'm doing fine, thanks. Your username is accurate though.

reply
(hackeridiot12 may be Jewish - IME Jews often type "G-d" because spelling the deity's name in impermanent text is disrespectful. Bit odd from my perspective, but harmless :))
reply
[flagged]
reply
> the easiest time to get a job was quite recent, in the back-half of COVID

Things can be easy or difficult at different parts of the hiring funnel.

Towards the end of covid, it was easy to convert a resume into interviews, and successful interviews into a job.

But in the 1990s the tech industry hadn't yet invented the five-interview, live-coding, culture-fit, hiring-committee gauntlet. If a hiring manager liked your resume there'd be one interview, and it wouldn't involve any coding.

reply
Annecdata: 1996-1999 was super easy, one round start next Monday. 2000-2003 difficult. Easy again until 2008. Hard till 2013. No data since then.

What I hear about today seems crazy hard.

reply
Late '90s were crazy easy compared to anything since. If you could demonstrate any amount of technical skill you were in.
reply
I got my first job by meeting someone on a train Thursday night and starting on Monday morning! (1998)
reply
Shortly before the .com bust, I was offered a job if I was willing to drop out of college.
reply
2004-2007 was hard for me in my experience.
reply
During the dot.com bubble, so many folks went to work for startups that old-fashioned corporate IT (in insurance, industry, banks) was struggling to hire. The saying goes that they hired you if you could spell "C++".
reply
In 1996-1998+ they had something called the Brass Ring job fair in the Santa Clara convention center in the heart of Silicon Valley. Employers would set up booths and some would hire people on the spot.

2021-2022 was pretty good as well.

reply
How you handle employees after the layoff announcement is a much easier conversation: Give them a lot of dedicated resources to navigate it and give them a good parting offer.

Nobody ever seems happy about how the announcement part is done though. "Wait for everyone to have 1:1" and the problem is the mass panic that starts to roll through the workday as employees wonder if they are next. "Mass announce and then engage after" makes another group upset they were told by a generic mass email. I've been at places which have gone each way and I'd honestly rather hear from the mass email myself.

reply
The 2010s were not that easy to get a job in. It took quite a lot to actually get a job. It didn't take 6+ interviews and takehomes. But you could use a recruiter, go through the interview etc.

There was no leetcode and the resources weren't great. The introduction of leetcode made everything super painful.

reply
deleted
reply
I mean, not to snarkpoast on main, but all of this has happened before re:

> The massive sudden shift in the commoditization of human workers and turning them into faceless labor resources that can be inhumanely disposed of with a keystroke

Look up the treatment of labor during the industrial revolution. Similarly then large competitive advantages in automation lead to concentration of power in the hands of those that (not to spill the beans on where I'm going with this) controlled the machinery and means of production by way of access to capital. Collective bargaining of some form by labor was (and I would maintain, still is) a reasonable response, as is state regulation. Not to literally use the M-word* here but ... these problems aren't new, and solutions have been explored in the past (not that they were or are perfect!). As is typical in tech, we could stand to learn a bit from history when considering paths forward from the present. History may not repeat verbatim but it sure as hell rhymes.

idk, just my two cents as someone in the technical trenches who happened to fall in love with an historian. :)

* Marxist/ism. The communists certainly had/have their problems, as did Marx's analysis itself, but he wasn't wrong about there being some society-scale Problems with unfettered capitalism.

reply
In much of Europe, if you're planning redundancies above a certain (low) number of employees, the employees / unions has a consultation right before layoffs start in order to be able to negotiate or consider other options...
reply
No, Salesforce.
reply
Oracle?
reply
My first task at my last job was removing access to an employee being let go. I had just gone through onboarding so I knew every (documented) service we needed to handle. We live tested it on my own accounts, measured the time before I noticed, and then proceeded to successfully go through the checklist.

Except not everything was properly documented, and it turned out the employee had given admin rights on some resources to a contractor which proceeded to wreak havoc on their behalf (the 'rm -rf' kind). Eh!

reply
Is this specific to US culture? And what about your work environment makes it such a risk?

Where people are laid off here (Norway), they're still employed by law for 3 months. Most companies don't force you to work all that time, but it's pretty common to finish up your tasks, do offboarding etc for a few weeks. Never considered it an issue. Maybe it's a high trust society thing?

reply
>Is this specific to US culture? And what about your work environment makes it such a risk?

It's called garden leave, it's popular everywhere, especially if it's a big international company with diverse workforce, sensitive to IP rights, since there's been plenty of cases of people taking company IP on USB drives to the new employer, like that Indian guy who took IP from Valeo to Nvidia and got his home raided by the police because the Valeo guys saw him share it on a Teams call lol. Same for companies in finance or that handle sensitive information. Norwegian trust doesn't fly anymore when it comes to multinational corpos.

Companies run on liability and risk mitigation. If something bad happened once (IP theft or sabotage from someone they let go), then they have to prevent from ever happening again, not keep blindly trusting people while letting it happen.

reply
It is not that common in Norway. It has at least been argued in the past that working your notice period is not just an obligation to employer if they want to enforce it, but a right for the employee on the basis that being walked out can affect your reputation by implying possible misconduct exactly because it has generally been uncommon in Norway.

I haven't worked in Norway for a long time, so haven't kept up to date on the current legal position. The typical argument used to be that if there were concerns over IP theft or sabotage, there were other ways of protecting against that - and indeed, insider risk is something companies need to deal with whether or not someone has been fired.

reply
> working your notice period is not just an obligation to employer if they want to enforce it

And what if they don't want to enforce it? Which is what I was talking about.

reply
Garden leave isn't for when you don't want to force people to work out their leave, but when you want to force them not to, and as the very next clause of my comment pointed out ("but a right for the employee"), it's not a given you can just do that in Norway. Most of the time, employees will be happy to be told they don't need to show up. Sometimes they aren't. There have been lawsuits over attempts to force people on garden leave in Norway.
reply
What's stopping people's from doing that while employed? I think if you treat your employees with respect, they don't feel the need to this kind of retaliation.
reply
So stealing IP, breaking the law and your contractual obligations, should be allowed if you feel like your employer isn't valuing you enough?

That guy was a six figure paid SW engineer, who stole IP for the opportunity to jump ship to an even better paid gig at Nvidia, not a minimum wage fast food worker who couldn't take it anymore.

Scammers will always be scammers and will use any excuse and opportunity to get ahead, no matter how much you trust, value and pay them, they'll always want more from you even when you have no more to give. They'll bankrupt you gladly if they can get away with it, out of greed, envy, spite and malice, I saw this when my parents ran a small business.

In globalized multinational companies, you can't defend from this using mutual trust and respect, only by strict IP protection, law enforcement, fines and jail time as a deterrent.

reply
> So stealing IP, breaking the law and your contractual obligations, should be allowed if you feel like your employer isn't valuing you enough?

Please don't straw man me. Discuss in good faith, and don't invent things I didn't say. I never said anything remotely close to that being allowed. I said that it could happen even if you don't terminate all their accesses the moment they're let go. And the fact that some people have to worry about it reflects on how the employer behaves or the trust in the society.

reply
deleted
reply
>Please don't straw man me. Discuss in good faith, and don't invent things I didn't say.

I'm not. That's just the only logical takeaway from your comment saying: "I think if you treat your employees with respect, they don't feel the need to this kind of retaliation."

How else would you interpret it, rather than a veiled threat that if employees don't get their way then they'll steal or sabotage you? Please explain in detail. If you feel you're not treated the way you want to, then quit and find another job, don't steal or sabotage your employer.

> I said that it could happen even if you don't terminate all their accesses the moment they're let go.

Yeah, but it's WAAY more likely to happen AFTER you give them notice of termination since breaking relationships be them romantic or employment, can cause people to do illegal things like steal from their employer or murder their spouse in an impulse of revenge, when they hear their relationship is being terminated. All this is documented from decades of police and legal records, and companies know this, so they take preventive measures.

>And the fact that some people have to worry about it reflects on how the employer behaves or the trust in the society.

Companies worry about it because some people are gonna be evil thieves no matter how well they're treated.

If you want to get better treatment then negotiate better, talk to lawyers, organize in unions, vote, go protest, pester your representatives, but don't break the law or steal from your employer in revenge, as that reflects badly on all workers, and the economic, legal and societal costs of a few thieves will be distributed on the honest ones in forms of more workplace surveillance, higher cost of doing business, higher insurance premiums, etc all of which have a negative upstream effect on wages and employment opportunities.

reply
You're kinda proving my point, though. It seems you live in a low-trust society where it's eat or be eaten, and where employers and employees regard each other with disdain. So your only way of interpreting my statement is that it's a "threat". But it's not, it's about mutual respect and good relationships.

Which is what makes it hard for you to fathom it doesn't have to be that way you experience. When my company laid of half it workforce two years ago, everyone stayed for a few weeks to help in the transition, with the same accesses as before. Because we were treated nice all the years working there, and with respect during the process, it was absolutely no ill feelings or any risks of people doing what you describe.

So again, please read and answer comments in good faith. It's your mind that's not open enough for alternatives here, please bear that in mind - don't use your own closed mindedness to misread my comments.

Edit: your other comments in this thread shows you absolutely loathe your employers. I feel sorry for you having had those experiences, but don't assume they're global.

reply
I have had this (garden leave) specified in contracts in Norway too - it's not strictly a requirement that you're allowed to serve out the full 3 months, but the default unless specified is 3 months. In the cases I had it in the contract, the contract generally framed it as if some other perk (like shares) served as consideration for giving my employer the right to put me on garden leave.
reply
It is common in the UK for people in certain jobs. I think the commonest reason is to make it harder for them to take clients with them.
reply
There's the classic article by Matt Ringel and Tom Limoncelli back from 1999:

https://www.usenix.org/legacy/event/lisa99/full_papers/ringe...

reply
I experienced that once. The parent and the parent's parent company were from the USA. The top CEO and CTO came over and fired everyone. My laptop was controlling a job that had to run pretty long on a 16 core server, but I did as asked: I shut down the laptop and left it on my desk. That was at least $50k down the drain.

The reason they fired the whole dept. was that they were going to centralize development, as they had 200 other developers. After 5 years, they still hadn't developed a new product. Then they bought a competitor and rebranded it. The old product had to be kept running for years after. I guess they finally switched all their clients, because the web sites now open with <!--eslint-disable @angular-eslint/template/prefer-self-closing-tags-->. Who puts that in their HTML?

reply
But I'm guessing that doesn't work with someone who's been collecting other logins:

> Muneeb had been assembling usernames and passwords—5,400 of them taken from his own company’s network data.

reply
Though you'd want to make sure there's no essential information that only this employee knows, because that action might terminate that employee's desire to cooperate with the company.
reply
I've turned off my own access at least three times when being let go from different jobs
reply