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

Post by michaelcampbell » Fri, Feb 09, 2024, 2:46 PM UTC

washadjeffmad wrote: post #193

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…

We tried at first, but we were so overwhelmed by the rate of deaths from the earliest moments of the pandemic that the org couldn't keep reporting them. It was a demoralizing effort for HR to try to put something, even a few words together for everyone, and it's left a lasting pallor where vibrant personal touches once were. People continue to vanish, and there's still no notice that, or how, they've moved on. Our Ge…

Post by michaelcampbell » Fri, Feb 09, 2024, 2:48 PM UTC

svat wrote: post #23

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 do something similar but instead of `|| exit 0` I use `--allow-empty` on the `git commit`. I don't mind the empty commits this creates, as they let me know that there was a successful automated run that happened to be empty, rather than having failed to run for whatever reason.

Post by donkeyd » Fri, Feb 09, 2024, 2:49 PM UTC

lotsofpulp wrote: post #261

donkeyd wrote: post #228

Earlier quoted context omitted.

> The rules on this vary across Europe Not really, ECHR has already ruled on this. It's pretty much only allowed if there's an important reason for it. For example, to recover something invaluable (contract, code, report) that isn't available somewhere else and cannot be replaced. In that case that's also the only thing that them employer can look for. They can't open obviously unrelated e-mails. So before talking to…

What mechanism is there to prove who looked at what emails? And who would be there to enforce it, especially at a small business?

Post by azemetre » Fri, Feb 09, 2024, 2:57 PM UTC

omgbear wrote: post #284

A former company I was at was really weirdly tight-lipped about people leaving. I'm sure totally unrelatedly, we got dinged a bunch on our SOC2 reports improper "off-boarding" and not removing access from terminated folks since no one knew to remove them. Once we added quarterly SOC2 controls to make sure only employees had accounts it was always a shock to see who had to be removed. I know the intent was to improve…

Post by Angostura » Fri, Feb 09, 2024, 2:59 PM UTC

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…