Ten Lessons Learned as a Technical Communicator — Interview with Rahul Prabhakar
Listen here:
You can download the MP3 file, subscribe in iTunes, Google Podcasts, or other podcast platforms.
Rahul Prabhakar talks with us today about ten lessons he has learned as a technical communicator. Rahul is an Indian technical writer living in South Korea working for Samsung. You can read more about the lessons he talks about from his ten lessons learned post.
Here's a snapshot of the 10 lessons:
- Lesson 1: Choose the Right Words
- Lesson 2: Strike a Rapport with Your Audience
- Lesson 3: Pay Attention to Details
- Lesson 4: Meet the Expectations
- Lesson 5: Break the Mediocrity
- Lesson 6: Know Your Role Well
- Lesson 7: Steer Away from the Usual Rut
- Lesson 8: Don't Network for the Heck of It
- Lesson 9: Education is only a Catalyst
- Lesson 10: Don't Suppress the Writer in You
Sponsored content
Links mentioned in the podcast:
- Technical Writers of India (TWI) mailing list info
- To subscribe to TWI, send an email to [email protected]
- Rahul's blog
- Holly Harkness's blog
- DMN Communications Podcast
- Harry Miller's podcast
- Music from Podshow
Contact Rahul at [email protected]
Contact me at [email protected]. You can also view my blog.
About Tom Johnson
I'm a technical writer / API doc specialist based in the Seattle area. In this blog, I write about topics related to technical writing and communication — such as software documentation, API documentation, visual communication, information architecture, writing techniques, plain language, tech comm careers, and more. Check out my API documentation if you're looking for more info about that. If you're a technical writer and want to keep on top of the latest trends in the field, be sure to subscribe to email updates. You can also learn more about me or contact me. Finally, note that the opinions I express on my blog are my own points of view, not that of my employer.