Best Programmers

  • Subscribe to our RSS feed.
  • Twitter
  • StumbleUpon
  • Reddit
  • Facebook
  • Digg

Tuesday, 19 August 2003

Re: [twin] Course Content for Technical Writing

Posted on 11:56 by Unknown
Hi
Your hard skills are okay. But you are not specific when you say 'team
skills' I mean today everyone is expected to be a team player so it is not
necessarily a skill you know? I'd rather focus on specific skills
like 'interviewing skills' and 'survey skills': a tech writer spends lot of
time interviewing subject matter experts and technicians to collect
information.
And on the technical front I strongly recommend they understand and learn
SGML, XML, HTML (stuff like the docbook DTDs is important). They have to
understand Mark up languages in order to write something that can be
published anywhere (cross platform). You may want to add in tools like
robohelp, framemaker PLUS a basic course on 'help' formats (winhelp, java
help, htmlhelp and so on).
A technical writer writes to an audience so her work has to be user-friendly
so you may want to include a primer on usability and usability testing. (I
can provide material on this)
I think a good technical writer is one that is not afraid of code, that is
ready to skim through reams of material, one that loves talking to people,
one that knows the rules of the language and knows when to break them. And
finally one that loves to write. And understand what 'being objective' is.

Hamsila wrote:
>
>Hi All
>
>I have been asked to help develop a post graduate diploma in Technical
>writing. This could possibly train novices in the field or those wishing to
>take up Technical writing as a career.
>
>As I see it, there are two sets of skills required:
>Hard Skills:
> Language
> Tools
> Editing
> Proofreading
>
>Soft Skills:
> Interpersonal skills
> Team skills
> Research skills
> Motivational skills
>
>Is there anything else that could be included?
>
>Regards
>Hamsila
>
>
>
>..........................000000000000................................
>Send messages to: twin@user.itconsult.co.uk
>
>Leave TWIN: Send blank email to twin-leave@user.itconsult.co.uk
>Join TWIN: Send blank email to twin-join@user.itconsult.co.uk
>Digest Mode: Send blank email to twin-digest@user.itconsult.co.uk
>
>Post Job-Ads: Send job-ad to: twinjobs@user.itconsult.co.uk
>
>List Owner: twin-owner@user.itconsult.co.uk
>TWIN Website: http://www.twin-india.org
>TWIN Archive: http://user.itconsult.co.uk/twin/archive/
>
>
>


Email ThisBlogThis!Share to XShare to Facebook
Posted in | No comments
Newer Post Older Post Home

0 comments:

Post a Comment

Subscribe to: Post Comments (Atom)

Popular Posts

  • Finding the voice
    Excerpt from LOUIS MENAND's review of Eats, Shoots & Leaves: The Zero Tolerance Approach to Punctuation” (Gotham; $17.50), by Lynne ...
  • Context Sensitive 'Sticky Notes': Stick a Sticky Note to your Blog!
    Conceptworld's Quick Notes Plus might appear like any other Sticky Notes Plus (QNP) program, but its context-sensitive notes feature is...
  • Use it before you write it.
    From the Nikkor ED 80-400mm f/4.5-5.6D VR Review (emphasis is mine): [quote] Here's the warning in the manual : "When the camera is...
  • Style guides: Sacrosanct?
    How many times have you paused and reflected, ‘man, I know I am right, but the style guide does not agree…’? For example, some style guides ...
  • (no title)
    Next STC Chennai Meeting On March 7 : This will be the second knowledge sharing session. The first meeting was a wonderful success and we h...
  • Wanted: Sr Technical Writer for Informatica Corporation
    Location : Bangalore Corporate Headquarters : Redwood City, CA Contact : Thao Diep, tdiep@informatica.com Job Description Responsibl...
  • The Personable Manual
    Why do product manuals sound formal and stiff-upper-lipped? Why don’t users read manuals? These questions have haunted the hallowed precinct...
  • Comments System: Anyone Can Post Comments Now!
    Folks, I know some of you were irritated by the fact that you had to login (if you're a Blogger user) or post as Anonymous while posting...
  • A brand name gone wrong
    "Did you know that Heroin was originally a brand name for cough syrup? In 1874, German scientists developed a formula for a painkiller ...
  • Promoting Document Usage: Taking a leaf out of Business Directories
    You can argue all day that you know a customer that reads your manuals but my point is that most don't. It is a blessing in disguise fo...

Categories

  • conferences
  • contigency design
  • culture
  • design
  • error messages
  • google
  • hall of shame
  • ideas
  • management
  • manual
  • standards
  • stc
  • strategy
  • tools
  • usability
  • writing

Blog Archive

  • ►  2009 (1)
    • ►  February (1)
  • ►  2008 (5)
    • ►  November (1)
    • ►  September (1)
    • ►  May (2)
    • ►  April (1)
  • ►  2007 (7)
    • ►  October (1)
    • ►  August (2)
    • ►  June (1)
    • ►  March (1)
    • ►  January (2)
  • ►  2006 (10)
    • ►  November (2)
    • ►  October (3)
    • ►  September (1)
    • ►  August (3)
    • ►  June (1)
  • ►  2005 (17)
    • ►  December (2)
    • ►  November (1)
    • ►  October (3)
    • ►  September (2)
    • ►  August (3)
    • ►  June (2)
    • ►  May (1)
    • ►  April (2)
    • ►  February (1)
  • ►  2004 (32)
    • ►  December (4)
    • ►  November (1)
    • ►  October (3)
    • ►  September (3)
    • ►  August (2)
    • ►  July (5)
    • ►  June (3)
    • ►  May (1)
    • ►  April (5)
    • ►  March (2)
    • ►  February (1)
    • ►  January (2)
  • ▼  2003 (42)
    • ►  December (2)
    • ►  November (3)
    • ►  October (1)
    • ►  September (3)
    • ▼  August (7)
      • Re: [twin] Course Content for Technical Writing
      • Latin Words Used in The English LanguageTrust me,...
      • Importing Word2000 Documents to RoboHelp HTMLArtic...
      • How to hire a 'Future-Proof' Technical WriterI cam...
      • AECMA Simplified EnglishWhat Is Simplified English...
      • And now, 'Technical Writer': The Movie
      • A Tale of a Technical Writer who did Programming f...
    • ►  July (2)
    • ►  June (1)
    • ►  April (4)
    • ►  February (4)
    • ►  January (15)
Powered by Blogger.

About Me

Unknown
View my complete profile