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

241–250 of 392 posts

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

#241

Post by JonChesterfield »

ElectricalUnion wrote: post #104
GauntletWizard wrote: post #26

Earlier quoted context omitted.

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…

Would fossil fit this bill? Somewhat git-compatible, based on sqlite3.

Specifically the fossil repo is a sqlite database.

I have a cron script stashing whatever is currently in an obsidian vault into a fossil repo. There's a fossil addremove command that makes that very easy. Thus distributed backups of said vault.

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

#242

Post by gpvos »

dudul wrote: post #237
gpvos wrote: post #208

Is it common in the USA that employees just disappear without getting the chance to say goodbye to their colleagues? At most places I worked, people tended to send a goodbye email to everyone@company and got a chance to say personal goodbyes, even when there was a negative reason for them to leave.

Yes it is common when the employee is being terminated. It may depend on the industry, but it's always been like that at the 10+ companies I worked at. Honestly, I much prefer it to the long notice (sometimes 3 months!) you get in say some European countries. Just rip the band aid and move on. Most likely you'll have a way to connect with former coworkers easily on LI and such.

A week or so seems fine to me. Gives you a chance to wrap things up and transfer stuff.

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

#243

Post by heads »

elromulous wrote: post #120
heads wrote: post #64

So negative! Where I work this tool is called “new-hires”. It uses a restricted read-only API key to our third-party people tool. It was given to me by our People Director . Sometimes there are lines beginning with - but the tool is named for the lines beginning with +. new-hires is built on top of the “people” python module / cli in our monorepo. That tool is so much more useful than just a way of diffing the org ch…

Where is this? Sounds like a great place!

Speechmatics.com in London and Cambridge, UK. We build audio and language models that perform the most accurate speech recognition available.

https://www.speechmatics.com/company/careers/roles

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

#244

Post by jijijijij »

simonw wrote: post #10

Love this bit: "Incidentally, if someone gets mad about you running this sort of thing, you probably don't want to work there anyway. On the other hand, if you're able to build such tools without IT or similar getting "threatened" by it, then you might be somewhere that actually enjoys creating interesting and useful stuff. Treasure such places. They don't tend to last."

> Incidentally, if someone gets mad about you running this sort of thing, you probably don't want to work there anyway.

If you do want to work there, though, maybe check the legal situation first...

I am almost certain, this counts as unauthorized processing of personal information. Just because you have access doesn't mean it's fair game to do whatever you like with it. Especially archiving, keeping a history or linking (external) data is not the intended use for such an interface. If you take the information home with you, e.g. on your work laptop, that may be a whole nother can of worms. May even count as business secrets you're exfiltrating.

At least in Europe, abusing such an interface likely would be illegal, certainly if you keep a copy/diff. Your employer may have to act against you, or become liable. Or they may use this misconduct later to conveniently terminate your contract (lol, especially, if you use your insights as leverage).

I presume the larger the network, the more likely this will get you in trouble. Conversely, collecting the data has little use otherwise.

How about you organize with your colleagues to voluntarily share employment information to gain collective leverage?

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

#246

Post by dudul »

gpvos wrote: post #242
dudul wrote: post #237

Earlier quoted context omitted.

Yes it is common when the employee is being terminated. It may depend on the industry, but it's always been like that at the 10+ companies I worked at. Honestly, I much prefer it to the long notice (sometimes 3 months!) you get in say some European countries. Just rip the band aid and move on. Most likely you'll have a way to connect with former coworkers easily on LI and such.

A week or so seems fine to me. Gives you a chance to wrap things up and transfer stuff.

Or roam the hallway, do nothing but bitch and all.

If I'm terminated I'm not gonna care about wrapping things up, I'm out of there.

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

#247

Post by walthamstow »

M2Ys4U wrote: post #232
athoscouto wrote: post #230

Earlier quoted context omitted.

Are you referring to GDPR? Does it apply to employees too, or only customers?

GDPR applies to everyone in the EU/EEA/UK. They don't need to be a citizen, they don't need to have any sort of contractual arrangement with the data processor. If they're alive and identifiable, the GDPR applies.

So interesting that you say alive. There's always a some obscure bit of GDPR I've never heard of. Does a dead person not have PII?

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

#248

Post by pharmakom »

I once discovered that a very large org had AD configured in such a way that you could see “last seen at” timestamp for everyone profile in the company.

It would have been trivial to track everyone’s hours using this, which would likely have been unpopular.

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

#249

Post by jjkaczor »

Hahahahaha... So, I um have a very similar script that I manage for 'KTMJ' - it's not to find deactivated users, but to synchronize certain ldap attributes to another system. This organization is large enough (300k+ users) that typically, between the time that the script queries ldap, prepares the synchronization file, then actually performs the synchronization import which validates if each user still exists, there are already several hundred accounts that have been deactivated during that window and reported in an 'error' log file. (The actual synchronization and 'error' log file are outside of my direct control)

Why did I laugh maniacally?

Due to 'budget constraints' my contract is being terminated (they have just been through several rounds of layoffs, I was expecting this), my account will be one of the ones deactivated on the next monthly cycle - prior to that, I will have to handover the processing and expected 'deactivated' users 'error' logging behaviour to my replacements...

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

#250

Post by scarface_74 »

neilv wrote: post #133
scarface_74 wrote: post #105

Earlier quoted context omitted.

Surprisingly enough, as toxic as Amazon is, after I got Amazoned and made my choice to “leave Amazon and get a nice severance” instead of “try to work through the PIP and still get fired and only get a third of the severance amount”, they let me stay for a week to finish up a customer project. I worked in Professional Services. I told them that I really wanted to finish the work for a customer (large state organizati…

Sorry about getting Amazoned. They don't have a reputation as a place inspiring loyalty. But, at least in non-Amazon contexts, I absolutely know people who would say they wanted to finish up some work, and they'd mean exactly that.

Nah it was fine. I had a job offer two weeks after I left doing the same thing.

I knew after the first year that I didn’t plan on stay at Amazon for more than four years and I planned accordingly.

I was nine months and two vesting periods short. But the severance more than made up for one.

The longer version of the story.

https://news.ycombinator.com/item?id=38474212

Post reply on HN