Best Programmers

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

Thursday, 8 July 2004

Installing a gas stove: Why I think technical writers are important to this green earth

Posted on 04:59 by Unknown
This morning my wife woke me up from my dreams of swimming with the Dolphins in Mauritius and hollered, 'get the gas stove working man!'. Groggy eyed, I went to the kitchen and unpacked the stove. The burners kept falling off and there were no instructions on the stove or the packaging about how to fit the burners and the knobs. That was the easiest part, you can bring your eyebrows down.

So, I pulled the new gas cylinder that weighed a ton. I had to fix a regulator to the cylinder. A closer look revealed a seal on the mouth of the cylinder. I glanced at my wife who was watching my progress. 'Pull the seal off honey!', she purred, as if it was something even Bush would have figured out. I mumbled an incoherent retort and started pulling the strong wire that bound the cylinder and the seal. I pulled hard. No luck, the damn thing wont budge. I squatted and peered on the walls of the cylinder to find some information that would help me. Nope! No such luck. So, I pulled harder. And the wire cut my left-thumb. My left palm was all crimson. I was incensed. What kind of a manufacturer would ship some thing like a cooking gas cylinder without an installation manual? Bharat gas. Ah!


I squatted again and this I noticed an arrow mark on the seal. Out of curiosity I pulled the wire parallel to the ground (I was pulling it 'up' earlier) and the seal slipped off the cylinder's mouth. Neat! But hey, you know, I would have liked it better if some one had stuck a sticker or probably given a single-page manual on how to install the regulator. If you thought my troubles are over. Think again.





Overjoyed with the seal coming off the cylinder I pounced on the regulator and -you guessed it right - blinked. I rolled it around to find some directon, some snippet that could get me started. My wife started admiring the ceiling, suppressing her laughter. But dude that I am, I was least offended. I took the regulator and started jamming it on to the mouth of the cylinder. Nope. Things are never that easy. I tried everything from banging the regulator's head to dropping it off from a height on to the mouth of the cylinder. Nothing worked. It would just not sit and settle down in the mouth. Frustrated I was pulling up the regulator, and I discovered the slide lock around the regulator. Slide up the lock, sit the damn thing on the mouth, and let go! The regulator squatted firm on the mouth, like a drunk on a barstool. Simple, yes, but... Yeah, yeah if only some one has written it some where.

Now, if you thought my troubles were over. Think thrice. The cylinder supplies the stove with the gas using a reinforced rubber and steel hose. I had to fix the pipe on to the tiny nozzles of the stove and the regulator. And I managed to do it using sheer force. And lost more blood from the cut on my thumb. It is absolutely impossible for a housewife to do it.



As my wife made coffee on our new stove, I was thinking: We technical writers are an important link between products and users. We guide and direct a product's use. A rocket engineer might design a rocket, but who tells the astronauts how to use the loo or the inter-galactic phone in the darn rocket? You.

So, my technical writing friend, the world would be a miserable place without writers like us. Don't go on that cloud number nine yet. Relax. Come down here and listen to daddy: Please remember this poor guy that cut his hand while pulling off the seal from the gas cylinder. If you had had written that small note ('Pull gently, parallel to the ground.') he wouldn't have a cut his thumb today. Remember a product's use overrides the product itself. No use. No product. No user. No use. Follow this and you will be able to afford those cruise trips, and yes, Dolphin watching in Mauritius.


Write to me: Suman[at]techwritersindia[dot]com

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)
      • Wanted: Sr Technical Writer for Informatica Corpor...
      • Style guides: Sacrosanct?
      • Wanted: Technical Writers for Wipro Technologies, ...
      • Job openings for young under-grads and graduates i...
      • Installing a gas stove: Why I think technical writ...
    • ►  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)
    • ►  January (15)
Powered by Blogger.

About Me

Unknown
View my complete profile