Best Programmers

  • 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: Posts (Atom)

Popular Posts

  • 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...
  • Participative Help Design
    Participative Help Design I used a weblog script to create online help for -uh- using weblogs. I used a plugin to pull help topics as alphab...
  • 3rd STC Chennai Meet this sunday.
    3rd STC Chennai Knowledge Sharing Session this sunday, April 4th. This month's knowledge sharing session will be held this coming sunday...
  • Firefox: Tech writer friendly!
    Firefox has an in-built popup blocker. Firefox saves your screenspace through its tabbed-browsing feature. Firefox allows for opening mult...
  • Engrish!
  • 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...
  • 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...
  • Finding the voice
    Excerpt from LOUIS MENAND's review of Eats, Shoots & Leaves: The Zero Tolerance Approach to Punctuation” (Gotham; $17.50), by Lynne ...
  • 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...
  • Tech-writers – A Necessary Evil
    In a world where accuracy is all important, a lot goes over the head of the dummy. I don't know if it's intellectual snobbery, but p...

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