“sure yes you can hard code everything. You’d just go against basic coding conventions. The way i am being treated is making it hard staying technical. Even when the versions are being hard coded it doesnt resolve the problems with the files. But like you demand i wont say anything anymore and try magic to fix these files.”
So i wrote 2 whole things, explaining all analytical steps i took and again that i didnt say i can not connect to the files but the files cant be altered Connection: yes Query: no
From my own autistic experience, people tend to get irritated when I try to explain my reasoning or analytical steps too much. At some point, you just have to accept that they’re not gonna get it.
When I’ve had a similar situation (much less hostile, thankfully), I just implemented it as told, documented it and let it break to show them why it wasn’t working. They took me seriously after that.
But also, when you’re on the way out anyway, don’t put too much effort into doing things “right”. You don’t owe them competence. They already think you’re incompetent. If they want you to add tech debt, that’s the most legitimate way to take revenge.
I wish they’d put me on leave like i asked when i got told i get laid off.
Honestly, it’s very reckless of them to not do so. I know we had an incident where a laid-off colleague (well, contract didn’t get extended, but the result is the same) pulled some nasty shit on his last day. Management learned from that and the next time they had to fire someone, they first revoked all access, then had them surrender all company devices and wipe company data off their private devices with security watching, then put them on leave for the rest of the contract. Just safer that way.
(This is not an encouragement to take any revenge on them. That might land you in legal trouble. But you can’t get in trouble for doing exactly what they tell you to. If their instructions are stupid, that’s not your problem.)
This company, and i know it, leaves me wanting to from now on build even less friendly ties to collegues of future companies
I think the difficult part is figuring out which of your colleagues are worth building ties with. I have some that I’m friendly with, some I’m more “professional”, some I pull a face when I see their message pop up and put off reading it for as long as I can.
From my own autistic experience, people tend to get irritated when I try to explain my reasoning or analytical steps too much. At some point, you just have to accept that they’re not gonna get it.
When I’ve had a similar situation (much less hostile, thankfully), I just implemented it as told, documented it and let it break to show them why it wasn’t working. They took me seriously after that.
But also, when you’re on the way out anyway, don’t put too much effort into doing things “right”. You don’t owe them competence. They already think you’re incompetent. If they want you to add tech debt, that’s the most legitimate way to take revenge.
Honestly, it’s very reckless of them to not do so. I know we had an incident where a laid-off colleague (well, contract didn’t get extended, but the result is the same) pulled some nasty shit on his last day. Management learned from that and the next time they had to fire someone, they first revoked all access, then had them surrender all company devices and wipe company data off their private devices with security watching, then put them on leave for the rest of the contract. Just safer that way.
(This is not an encouragement to take any revenge on them. That might land you in legal trouble. But you can’t get in trouble for doing exactly what they tell you to. If their instructions are stupid, that’s not your problem.)
I think the difficult part is figuring out which of your colleagues are worth building ties with. I have some that I’m friendly with, some I’m more “professional”, some I pull a face when I see their message pop up and put off reading it for as long as I can.
Some companies are shit. Not all of them are.