zlacker

> Not the same but I was sacked during a probation period because I refused to give my proof of ID details a 5th time to the HR, the same 3 pieces requested multiple times or lost. I told them to reuse those I uploaded a day or two earlier.

That's no way to survive a career (as you found out). That's the kind of thing you use to build team camaraderie, after the 3rd time or so start posting about it in the team chat, if you're in an office put up a little sign saying "it has been ## days since I was asked for my ID", play along with any jokes about it, that sort of thing. And also politely ask your manager what's going on, and if that's normal, and send a polite email to the HR manager.

I get that it's a nuisance, but surely it couldn't have been more than a few minutes out of your day every time (and getting faster with repetition, right?).

> (yes they were average developers there at best)

Sour grapes?

>>bigbil+(OP)
Yeah the ID was kind of personal at the time, identity fraud was at the forefront of my mind because HR had no idea where the uploads that they had confirmed, and I'd seen emails for, had gone. One partial loss initially I could accept, two was a bit much, three started taking the piss, fourth was the last and final, and I stated I was now uncomfortable giving - which they fluffed again. Honestly that level of incompetence sounds like a downright lie, but people like that actually manage to keep a job, probably by firing the likes of me that point out their errors.

Not really sour grapes btw, without going into depth that would giveaway the employer, the 3 devsnthat I worked with had been unable to implement functionality that had been invented within the last 5-10 years because they never did their own research or keep up with trends. As an analogy think akin to them only ever using traditional SQL DBs, then being shown a massive serverless distributed db that didn't use SQL, that required software redesign for eventual consistency, couldn't do ACID transactions, all needed for a small high value, short deadline project, and you get some idea of the scope of change and steep learning curve they struggled to address. I'll restate this is not the actual problem, but the scope and impact is of the same size.

If that's sour grapes by your definition then ok :), but for me for BE devs around my own age, it seems a little underwhelming.