I have a head full of stuff that hasn’t had time to be documented, and being a single point of knowledge isn’t job security, it’s a major risk.
My code gets documented. But so much infrastructure is just held in my head as senior SysAdmin. Wherever possible I just have a ride-along “up-skilling” (works like a RAID mirror for my brain).
I came across this early in my career in networking. I ended up having to support another technicians customer(we primarily managed our own workloads) and he did not use the tools(vault) we had to manage the network equipment credentials, so I always had to call him and ask him what the password is and why he doesn’t update it in the vault(it frequently changed) … After bothering him enough about it he said it was job security.
This was a 45k entry level job that he was years into. Why someone would want job security at the bottom part of the totem pole is beyond me, but that is where I mostly came across tribalistic tendencies(I worked in a lot of small/medium sized companies before getting a big break)
If I look up those people on LinkedIn, they’re exactly where they were or in another lateral position. They don’t tend to make it very far.
lemmy.ml
Newest