Quote:
Originally Posted by Sarlacc
Well... Writing documentation is generally perceived by engineers as a tedious and boring task, so it's usually assigned to the new clown or the clown who's never busy with important stuff. Or it's postponed until it's too late.
|
Or assigned to the product team who decides that the "documentation is in the experience" and tells the support engineers the product doesn't need documentation... nevermind said support engineers have dozens of clients asking for precise instructions on how to use it because they can't figure it out.
And then the senior support engineer (i.e. me) ends up having to spend her lunch break writing the documentation just so her team doesn't have to keep typing the same email over and over and over (because she doesn't have enough to do that's actually in her job description), only for a sales rep to complain that the documentation isn't "pretty enough".
Hire a damned tech writer already.
