Job thread
HaemishM:
I built all of our websites, have had multiple in-person training sessions about them, and when I got the first one done a few years ago, I spent weeks on a manual complete with screenshots about how to edit the site. That information is mostly out of date now, but for the most part, the ones I trained only use the little slice that they need to use to do their regular jobs, and barely touch anything outside a very narrow focus. Hell, I even went so far as to train multiple people from different divisions to edit just their own content. I can count on one hand the number of people who actually used any of the training I provided, rather than just sending me emails when they need something changed.
People are lazy.
Samwise:
The astonishing thing is how much more time and effort some people will put into getting someone else to do their work for them than they would have if they figured out how to do it themselves. I'm too lazy to be that lazy.
Chimpy:
I was on a call with one of my former coworkers and one of the guys who replaced me this morning to give guidance on a software update for a product that I am an expert on that they haven't upgraded since I left 2 years ago and the new guy thanked me for "all the documentation you left, it has been very helpful".
And I did almost NO documentation because I was too swamped to write stuff up because I was doing all the server/storage/networking/cloud architecture and administration.
So there are people that use information provided to them, but they are definitely rare.
Samwise:
That or he was just kissing your ass. :why_so_serious:
My first week back at the job that I recently quit (again), the guy who had putatively replaced me told me how he loved the paper I'd written on some algorithm or other. When I (naively) asked him for details (what ideas did he have for further development? what questions did he have?) he kinda stammered something about how he'd read it a few times and it wasn't totally clear to him yet but he slept with a copy of it under his pillow (he literally said this) and every time he re-read it he got something new out of it. Bitch, it's not a poem, it's a technical document. I immediately identified him as a halfway competent ass-kisser and entirely incompetent bullshitter, and I revised that estimation further downward in the year and a half of working with him that followed.
Chimpy:
I said "that's funny because I didn't really write much documentation" and he specifically called out what it was he was speaking of which was stuff like: hardware inventory which included all the relevant hardware addresses and machine serial numbers, naming convention notes, and the comments added to firewall rules and such.
Mostly stuff I made for myself to keep track of things. (And also to fulfill audit requests, of course)
Navigation
[0] Message Index
[#] Next page
[*] Previous page