That fits a lot of tech writing also: we save users time! We get to be the ones who thrash around all week, get pissed off, want to quit -- then finally get it and capture what we learned in a doc. Especially true with my tech-writing students at Austin Community College (Austin, Texas).
Indeed. Tech writers are super heroes working behind-the-scenes to improve the overall experience. If only we were in charge of everything (oh, wait... that might not be a good idea, in retrospect). 🤠
I like to say that what I do when I create developer docs is to save the reader time. Most devs are pretty smart, and given enough time, can figure out what a function does, and so on. I save them that time.
Hey! I can run a lemonade stand! But a small one, mind you. -- dmz
That fits a lot of tech writing also: we save users time! We get to be the ones who thrash around all week, get pissed off, want to quit -- then finally get it and capture what we learned in a doc. Especially true with my tech-writing students at Austin Community College (Austin, Texas).
Indeed. Tech writers are super heroes working behind-the-scenes to improve the overall experience. If only we were in charge of everything (oh, wait... that might not be a good idea, in retrospect). 🤠
I like to say that what I do when I create developer docs is to save the reader time. Most devs are pretty smart, and given enough time, can figure out what a function does, and so on. I save them that time.
That’s a valuable service and worthy of recognition.