- cross-posted to:
- programmer_humor@programming.dev
- cross-posted to:
- programmer_humor@programming.dev
You must log in or register to comment.
We recently had to buy out a director that kept all the technical knowledge to themselves for the last 20 years. They were almost always available 24x7 for outage calls and it became clear his teams didn’t know shit about anything, especially when said director was sick or on vacation. He was labeled a danger to the infrastructure and settled for a multimillion dollar buyout with a full knowledge transfer. Retirement age, fat 401k, company stock and other investments… yeah, he took that deal immediately, like no hesitation.
There are people at my job like that and it’s so annoying. They never answer any questions about how they do things, so I’m having to reverse engineer their solutions if they decide not to be available lol
It’s so frustrating how successful soloing information in corporate environments is
As a John in both name and in relation to my main project at work, I am working my ass off to write comprehensive documentation and to train the rest of the team to take over. I don’t wanna be working on this same shit in 5 years.
Remember kids, make your code as confusing as possible. Clear documentation just makes it easier to replace you.
