Comments on: Ten Lessons Learned as a Technical Communicator — Interview with Rahul Prabhakar

By: Tom

Tom — Fri, 09 Oct 2009 15:56:08 +0000

Nirmala, I like your point about not abandoning some creative style to the prose, keeping in mind that it will be read by a real human being. Thanks for the comment.

By: Nirmala Rao

Nirmala Rao — Wed, 07 Oct 2009 04:18:24 +0000

True, writers sure should not restrict their creative writing abilities due to the fact that what’s being written is a technical manual – after all it’s read by the end user. At the same time give the user what’s required in a simple and pleasant way. It’s only balancing both – should be a good read aa well as what’s required!

By: raid

raid — Fri, 03 Apr 2009 18:14:42 +0000

im trying to get readers to my blog too and was wondering if i could purchase a link in your blog roll via paypal? let me know – thanks

By: Jamorama Reviews

Jamorama Reviews — Sat, 16 Aug 2008 12:11:13 +0000

This will help any one wanting to progress in the tech field. Thx for the post.

By: Tom

Tom — Tue, 05 Feb 2008 03:34:29 +0000

It is an interesting comment, not suppressing the writer in you. It all depends on how one defines the term “writer.” Writers certainly use skills of organization, clarity, focus, accuracy. But usually the word writer conjures up associations of novelists and creative types. I do think creativity and innovation are huge parts of the IT industry. And these are the key traits of writers. You have to create a product manual out of nothing. You have to communicate complicated concepts. You don’t have to write everything in dry, short Dick-and-Jane type sentences. You can add some flair and style.

By: Ram Venkatraman

Ram Venkatraman — Mon, 04 Feb 2008 07:50:57 +0000

I disagree with “Don’t suppress the writer in you” part. Technical writing is intended for an audience and with a purpose. Unlike creative writing, technical writers can’t take the liberty. The message has to be precise and unambiguous.

May be blog, like Prabhakar, to show the writer in you. But, with a manual, just be a technical writer.

By: Ten Lessons Learned as a Technical Communicator — Interview with Rahul Prabhakar | I'd Rather Be Writing

Thu, 17 Jan 2008 03:52:40 +0000

[...] Ten Lessons Learned as a Technical Communicator — Interview with Rahul Prabhakar [...]

By: Ten Lessons Learned as a Technical Communicator « rahul,technical blog

Ten Lessons Learned as a Technical Communicator « rahul,technical blog — Tue, 28 Aug 2007 08:08:52 +0000

[...] full link http://techwritervoices.com/2007/01/13/rahulprabhakar/ [...]

By: Tom Johnson

Tom Johnson — Sat, 03 Mar 2007 23:00:10 +0000

Vandana, you might want to send Rahul an email with this request, as I’m not sure he checks this site regularly for comments. If you click the first link in this post, you’ll see a written version of the 1o lessons.

By: Vandana Sah

Vandana Sah — Thu, 08 Feb 2007 15:37:13 +0000

Hey Rahul,

the snapshot of 10 lessons are really too good to be true.
can i request you to send me these lesson in word / text format on my email id

your creative, active and technical mind give a inspiration to others

Keep it up…
Regards,
Vandana Sah