Technical Writing Tuesdays: You know you’re a tech writer… (part 1)

Posted on Tuesday, August 19th, 2008 in technical writing Tags:
This entry is part 12 of 15 in the series Technical Writing Tuesdays

I’m pretty busy with my new job this week, so this is just a quick post - but hopefully a fun one. I wanted to write a You know you’re a technical writer… list, but I’m low on innovation and humour at the moment.

So, I’m going to start the list, and I want you all to join in… and I’ll post up a revised list in two weeks’ time! Please bear in mind that although a lot of you who read this blog will definitely empathise with some of the entries, I’m looking for things from a tech writer’s perspective.

You know you’re a technical writer…

… when you feel emotional and/or physical pain at the sight of an out-of-place apostrophe.

… if, when faced with an engineer asking you questions about a product you document, you say in a tired or exasperated tone: “RTFM!”

… ???

————–
If you have any questions or comments about this article, or any suggestions for future posts, please comment on this post or email me via my contact form.
Technical Writing Tuesdays: index of posts

[Slashdot] [Digg] [Reddit] [del.icio.us] [Facebook] [Technorati] [Google] [StumbleUpon]

2 Responses to 'Technical Writing Tuesdays: You know you’re a tech writer… (part 1)'

Subscribe to comments with RSS or TrackBack to 'Technical Writing Tuesdays: You know you’re a tech writer… (part 1)'.

  1. no imageBrady (Who am I?) said,

    on August 20th, 2008 at 11:22 pm

    I’m not a Technical Writer… and this might be a bit off-color… but you asked for it.

    If you are dismayed to find out that periods do only come once a month for some people.

    Brady’s last post: A Dream Remembered

    Rate this:
    3.2

  2. on August 21st, 2008 at 11:53 am

    It’s definitely a bit off-colour - but still much less offensive than a comment that escaped my spam filter on another post.

    Come on writers - you can do better than this, surely?

    Rate this:
    3.1

Post a comment