Tech Writers

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

Thursday, 6 February 2003

Posted on 16:21 by Unknown

The Seven Deadly Assumptions of Technical Communication - William Rice



Years ago, as a young programmer/analyst on a project leader’s course, I made an assumption during a team exercise. Not a crucial mistake, you would think. I assumed that I had all the information I needed to complete the exercise. I also assumed that the exercise was about interviewing a potential employee. In fact, the exercise was actually about the danger of not identifying and confirming assumptions before blindly rushing on with the task at hand.



In this article, I identify seven areas in the field of technical communication where unconfirmed assumptions can lead to a waste of time and money and also undermine your credibility. Read more



Read More
Posted in | No comments

Posted on 08:17 by Unknown

Useful links for technical communicators



http://www.prc.dk/user-friendly-manuals/ufm/linklist.htm has some great links/resources. This resource is Edited by Peter Ring, PRC - Peter Ring Consultants, Denmark.
Read More
Posted in | No comments

Posted on 08:11 by Unknown

Dictionary of Plain Language



Found this on techcommunicators.com. To check out the dictionary go straight to: http://www.techcommunicators.com/diction.html Hope you find it useful.
Read More
Posted in | No comments

Saturday, 1 February 2003

Posted on 07:25 by Unknown

Online Help: Choosing a Tool



There was discussion on the TWIN mailing list about online help and Alfred had this to say about that:



Hi

Another issue with .chm is that you (the end user) have to download the entire file when you're accessing the help system. That might not be such a good idea if your users are accessing the app over a network. Usually for web-based applications people tend to use a HTML-based help system (like WebWorks Help 3.0) or just plain HTML with searching and indexing capabilities.

I would advise you to think about these issues (and others) before picking a tool or a format. RoboHelp might be used by everyone in India (just as an example) but it might not be the best tool for you. Maybe AuthorIT does what you want. Evaluate the tool, its limitations and whether it does what you want it to do. I guess what I am trying to say is that you should make an informed decision.

Alfred

Read More
Posted in | No comments
Newer Posts Older Posts Home
Subscribe to: Comments (Atom)

Popular Posts

  • 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...
  • Microsoft Longhorn Help: Highlights
    "Authors will develop content for "Longhorn" Help using an XML-based markup language called Microsoft Assistance Markup Langu...
  • (no title)
    The User-Friendly Manuals' Website The User-Friendly Manuals' Website
  • (no title)
    Interviewing the Techies My current project involves interviewing the architects, programmers and other experts. Here are some observations:...
  • (no title)
    Role of a Technical Writer: Mail to the TWIN List Let's look at it the other way around . There are still a lot of organizations that do...
  • 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...
  • (no title)
    How to save your client $1600 per task per year through Usability Testing I have noticed quite a few mails asking how to conduct a usability...
  • Hollywood May Hire You!
    Check this out. This is a brilliant observation: >"Screenwriting = Creative Technical Writing"
  • Writing SI units and symbols
    Quite a few of us do not write the SI units correctly. If you are a Physics or Chemisty student, and still remember what you studied in scho...
  • Technical Writing Glossary
    I think this is a neat idea and is an excellent resource for aspirants and practising pros alike. Check it out. http://members.iinet.net.au/...

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)
    • ►  July (2)
    • ►  June (1)
    • ►  April (4)
    • ▼  February (4)
      • The Seven Deadly Assumptions of Technical Communic...
      • Useful links for technical communicatorshttp://www...
      • Dictionary of Plain LanguageFound this on techcomm...
      • Online Help: Choosing a ToolThere was discussion o...
    • ►  January (15)
Powered by Blogger.

About Me

Unknown
View my complete profile