Don’t start unbelieving! Never don’t not trust your feelings!
I’ve been writing a handover document literally for years at this point. It’s mostly just for my own reference, but the day the next guy takes my position, they will hopefully be grateful for the effort.
I’ve been writing handover documents for my own consumption for the last 12 years at this job. It’s good practice for creating procedures for other people to follow when I don’t want to do a job (like repeating the procedure 15 times and thoroughly documenting the results then getting a committee of six to sign off on it…)
It also helps when somebody asks me how to do something I haven’t looked at in 5-10 years.
DO NOT NEVER SWITCH OFF
have you ever seen it play out like that? :p
Actually yes! I’m in an odd spot where I left for a couple years for another job and came back to the same company. Not only was the tech that was in my place while I was gone grateful, he actually continued to add to it so that when I came back, there wasn’t a whole lot I had to update!
I’ve been the recipient of such a document, and I was absolutely grateful. I’ve also been the recipient of absolutely no documentation. And I’ve written one and had it be appreciated when I laterally moved positions, which the 3 people who replaced me appreciated.
Depending on the enterprise environment and role, it can take up to 2 years to fully learn the system without such a document. Especially if it’s an esoteric field.
I’ve also been the recipient of absolutely no documentation.
Yeah, I took over for a guy who rage quit a year earlier, then his (hire the cheapest guy we can find) replacement basically didn’t make any progress so they hired me. First question: where is this undocumented build server that took six years to build, physically? Answer: in this tower case here… Second question: when was it last backed up. Answer: …turns pale and jogs over to IT.
So keep it on?
Except when you don’t.
Just make sure it is not never!
Now my brain hurts. 🤯
🤔 0 XOR !0=?
0 XNOR 0
