| ▲ | hilariously 5 hours ago |
| Right, this seems like an obvious conclusion - what is the outcome of the person writing the docs in either case: 1. Immediate better output from the machine OR...
2. Being sidelined for career promotions because you spent so much time making sure documentation was accessible while everyone knows they can ask you instead of reading it, and you will answer.
|
|
| ▲ | rufo 5 hours ago | parent | next [-] |
| re: #2: I'm in this description, and I am anguished by how much I do not like it. (reference: https://knowyourmeme.com/memes/im-in-this-photo-and-i-dont-l...) |
| |
| ▲ | hilariously 4 hours ago | parent | next [-] | | It's bad for us, but I imagine the tech writers feelings are even darker. They spent years being demonstrating how important good docs were, nobody in management cared, they were mostly laid off and discarded before there was even a credible replacement available. | |
| ▲ | tstrimple 4 hours ago | parent | prev [-] | | One of the clients I’m consulting with has one of the best cloud onboarding docs I’ve ever seen. Lays out exactly the services supported. Who does what pieces. What is self service. They break out latency differences between the cloud environments and on-premises. A serious amount of good work that’s incredibly useful working within their system. I use it frequently. Their head of cloud engineering has a permanent “away” message on Teams pleading with people to check the cloud docs first instead of just asking him directly. I would be frustrated too. |
|
|
| ▲ | 4 hours ago | parent | prev [-] |
| [deleted] |