A depiction of the world’s oldest continually operating university, the University of Bologna, Italy.- Image Credit, Wikipedia
Learning on the job is a great thing. But, is getting a higher education in Technical Writing after gaining some real-world experience a good choice as well?
I worked as a technical writer for eight years in New Delhi. Recently, I took a sabbatical to pursue a post-graduate certificate in technical communication from Seneca College, Toronto. The term sabbatical (from Latin ‘sabbaticus’, from Greek ‘sabbatikos’, from Hebrew shabbat, that is Sabbath, literally means “ceasing”) means – to take a break from work for an extended period of time, to pursue a goal.
Looking back at the golden triangle of cost, time, and scope, my decision to pursue higher education in technical writing after getting the real-world experience, was challenging and satisfying at the same time. I often felt that the learning outside the classroom is more important than studying in the classroom. For example, walking a kilometer to my class in -25 degrees, and under a heavy snowfall was as challenging as writing a technical autobiography for my technical writing class.
Read more >>
Like this:
Like Loading...
LinkedIn started out in the living room of its co-founder Reid Hoffman in 2002 and now operates the world’s largest professional network on the Internet with 161 million members in over 200 countries and territories. It is available in seventeen languages: English, Czech, Dutch, French, German, Indonesian, Italian, Japanese, Korean, Malay, Polish, Portuguese, Romanian, Russian, Spanish, Swedish and Turkish.
Reading is a primary form of communication for most people and they have different habits of reading. Not surprisingly, different people read product documentation in different ways. But how do they read and why should we care about their reading habits?
In order to publish an effective help documentation, you must gather as much information as you can about your audience. For most technical writers, audience analysis is the first, and perhaps the foundation step, in developing documentation for an end-user while following a documentation development life cycle (DDLC).
