Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Figure out who's leaving the company: dump, diff, repeat

rachelbythebay.com

Post reply on HN
Print view View original

141–150 of 392 posts

Re: Figure out who's leaving the company: dump, diff, repeat

#141

Post by picadores »

ThrowawayR2 wrote: post #27
jedberg wrote: post #9

Layoffs in the WFH era are weird. Back in the day you had a pretty good idea of who got laid off because you saw them walking out the door with a box of their stuff. You could go up to them and say, "hey let's meet at $local_watering_hole and hang out". You could swap contact info if you didn't already have it. You could get closure. Now, one day a bunch of people just stop replying to email. You have a to wait a whi…

I regret to have had a recent opportunity to notice that MS Teams shows an empty status icon for deleted/disabled accounts. Their documentation describes it as "status unknown": https://learn.microsoft.com/en-us/microsoftteams/presence-ad...

The user was disappeared

Re: Figure out who's leaving the company: dump, diff, repeat

#142

Post by Gabrys1 »

sillysaurusx wrote: post #125
yau8edq12i wrote: post #109

Earlier quoted context omitted.

What? First, Europe isn't a single country and there are large difference between legal systems. Second, what you said is just plain wrong in at least one. In France (which is known for strict worker protections) the employer can go through any employee's mailbox or files on their work computer/account provided 1. that the messages/files in question aren't clearly marked as personal 2. that the conditions for the acc…

I had some DM’s which were of personal nature that were rifled through after a contract ended. How do you "clearly mark a DM as personal"? It was creepy, and further illustrated that anything you say in Slack can and will be viewed by the whole company. If not literally, then that’s how you should treat it. You might be right that it’s not illegal, but it would be nice to have those kinds of protections. Trying to ta…

> anything you say in Slack can and will be viewed by the whole company. If not literally, then that’s how you should treat it.

Anyone thought otherwise?

Re: Figure out who's leaving the company: dump, diff, repeat

#144

Post by the_gipsy »

economicalidea wrote: post #88
Aurornis wrote: post #48

Earlier quoted context omitted.

Watching people’s accounts go into deactivated status in Slack with no goodbye is sad. The most toxic boss I ever worked for would request access to former employee’s Slack accounts under the guise of looking for data to transition their job. Their accounts would periodically go green when he logged in as them. Spooky to see ex-coworker accounts go green and know the boss is scouring their private messages. I know co…

You can’t get private Slack messages easily if you don’t have direct access to the account. There is an audit feature on the Enterprise version that allows it, and you can appeal to slack to open the messages due to a crime or similar - but AFAIK on the normal plans you are out of luck of you want to read private messages as workspace owner.

And all but extremely early startups or cheapskate companies have the Enterprise version.

Re: Figure out who's leaving the company: dump, diff, repeat

#145

Post by saagarjha »

jedberg wrote: post #9

Layoffs in the WFH era are weird. Back in the day you had a pretty good idea of who got laid off because you saw them walking out the door with a box of their stuff. You could go up to them and say, "hey let's meet at $local_watering_hole and hang out". You could swap contact info if you didn't already have it. You could get closure. Now, one day a bunch of people just stop replying to email. You have a to wait a whi…

After going through my first layoff (not affected personally, I just saw people who were), I just started posting my personal contact information preemptively. I've seen others start to do the same. It's kind of depressing but I think it really helps to be able to reach out after the termination is done.

Re: Figure out who's leaving the company: dump, diff, repeat

#146

Post by TeMPOraL »

at-fates-hands wrote: post #66
kristopolous wrote: post #60

Earlier quoted context omitted.

The lockout always struck me as dumb and I didn't do it as a manager. If I trusted them for the 3 years they worked for me, I can trust them for another week or two. Tie up loose ends, take your time. We're all adults here. I understand that under the worst circumstances bad things can happen but that's always the case.

I worked at a large web dev company and for years they had this attitude. Then one designer put in his two weeks and spent the majority of the time downloading all the site files for all of the sites the company had built over the two years he was there. We're talking hundreds of static sites where he took the all the design docs and static HTML/CSS/JS files one would need to recreate them somewhere else. Instead of…

> The one designer totally ruined the company from ever letting someone stay for their two weeks.

No, it's the over-reaction by whoever instituted that policy that ruined the company. They should've cut their losses and ignore the outlier, perhaps make it tad more difficult to copy off data en masse without being noticed, and/or do many other things addressing this risk without ruining the workplace for everyone else.

This is the organizational equivalent of autoimmune disease. Works at every scale. On national/international scale, this is what terrorist organizations are exploiting - do an X amount of damage that may even be counterproductive to their goal, and watch the victim do 1000X damage to itself by overreaction.

Re: Figure out who's leaving the company: dump, diff, repeat

#147

Post by saagarjha »

bsimpson wrote: post #82
jedberg wrote: post #9

Layoffs in the WFH era are weird. Back in the day you had a pretty good idea of who got laid off because you saw them walking out the door with a box of their stuff. You could go up to them and say, "hey let's meet at $local_watering_hole and hang out". You could swap contact info if you didn't already have it. You could get closure. Now, one day a bunch of people just stop replying to email. You have a to wait a whi…

During layoffs session last year, the company I work for immediately removed people from the corporate directory, and then went to the guy who had made the unofficial facebook and made him hide them in his tool too. They still technically worked there during the WARN period, so they didn't have epitaphs either. That went over about at well as you'd expect. This time around, the laid off people show up as on vacation.…

The infuriating part is when they spin this as some sort of employee privacy move, as if the employee (now ex-employee? But not really, because of WARN) has no input in that decision.

Re: Figure out who's leaving the company: dump, diff, repeat

#148

Post by rrrrrrrrrrrryan »

GauntletWizard wrote: post #26
simonw wrote: post #11

If you're going to run something like this, I thoroughly recommend using Git for it. You can have your cron do something like this: curl https://internal.corp/employees.txt > employees.txt git add employees.txt git commit -m "Automated: $(date -u)" || exit 0 The || exit 0 should ensure no errors even if there is nothing to commit Now you have a commit history of every change made to that source of information - just…

I've been seriously considering using Git for all sorts of oft-changing-but-rarely-majorly data. Lists of books in my bookshelves. The other problem is that I sorta want transactional-database features on top of these things. Git does this well. I also want fast indexing on parts. Git does not do this well. I am considering writing a "standard" for the dumping of sqlite to git, so that I can just delegate this out; A…

> oft-changing-but-rarely-majorly data

I think you're referring to SCDs, and there are plenty of well-defined ways to track these within relational databases:

https://en.wikipedia.org/wiki/Slowly_changing_dimension

Why git?

Re: Figure out who's leaving the company: dump, diff, repeat

#149

Post by saagarjha »

worthless-trash wrote: post #108
permalac wrote: post #71

Earlier quoted context omitted.

I work with identities. I've worked in Spain, France and uk. 99% of lay off are agreed and there is no need for account termination, my current company let's you have your account open 30 days after your last day, so you can move data out to your next company.

Sorry, move data out ? Can you expand on exactly what this means, as I imagine most companies would not want their data moved out to another company.

Presumably things like "your credentials to the account that we deposit RSUs into" or "your picture of the beer they served in the cafeteria one time that you liked".

Re: Figure out who's leaving the company: dump, diff, repeat

#150

Post by popcalc »

eddiezane wrote: post #55

Back when I was at DigitalOcean they were laying off/firing people from the company but not announcing any departures. You'd just go to message someone and their Slack account was deactivated. This was over the course of several weeks. I built a Slack bot to post when accounts got deactivated and learned of some new departures well before those impacted actually did. https://github.com/eddiezane/no-ghosties

It seems DO uses the same methodology for their customer support.
Post reply on HN