TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:Re: "Labs" vs. "Tutorials"? From:Janet Swisher <jmswisher -at- gmail -dot- com> To:techwr-l -at- lists -dot- techwr-l -dot- com Date:Mon, 29 Mar 2010 13:11:45 -0500
I agree with Gene that "Lab" doesn't really make sense to me in a
software world. Also, in the physical world, to me it implies an
open-ended task like "isolate such-and-such chemical", where part of
the student's contribution is to figure out the step-by-step
procedure. So, I wouldn't use that term for step-by-step procedures at
The distinction I would make is:
* If the student learns the content by going through the steps, it's a tutorial.
* If the student learns the content from some other presentation, and
then applies or practices it by going through the steps, it's an
On Mon, Mar 29, 2010 at 12:06 PM, Gene Kim-Eng <techwr -at- genek -dot- com> wrote:
> Having worked with products that are actually used in laboratories, I would say that lab instructions are guiding the reader through steps that use actual equipment, vs tutorials that use equipment simulations. I don't know what the distinction would be when the product is all SW and data and there is no physical equipment involved in the instruction.
> Gene Kim-Eng
> ------- Original Message -------
> On 3/29/2010 4:25 PM Michael Herman \(Parallelspace\) wrote:
> 1. When should these sorts of procedures be called Labs? .when should these be called Tutorials?
Use Doc-To-Help's XML-based editor, Microsoft Word, or HTML and
produce desktop, Web, or print deliverables. Just write (or import)
and Doc-To-Help does the rest. Free trial: http://www.doctohelp.com
Explore CAREER options and paths related to Technical Writing,
learn to create SOFTWARE REQUIREMENTS documents, and
get tips on FUNCTIONAL SPECIFICATION best practices. Free at: http://www.ModernAnalyst.com
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-