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: Imagine you teach From:Doug Nickerson <Doug_Nickerson -at- ONSETCOMP -dot- COM> Date:Tue, 22 Dec 1998 10:49:40 -0500
>If the course is a technical writing class for students in other majors
>(for example, majors in mechanical engineering), the focus on programming
>may or may not be useful.<snip> A course for these students would
concentrate not on on-line help or
>programming, but on workplace writing issues (including processes of
>writing in workplaces, document versioning, technical presentations,. ..
Hello Johndan Johnson-Eilola,
At the U. of Massachusetts at Amherst in 1989 or so, they
introduced a junior year writing requirement. I was in the computer
science
department so this course took the form of technical writing. The
professor didn't try
to give us new information about the software process, but rather talked
about
writing proposals, instructions, and so on.
I wish that course had been better. And I wish I knew what would have made
it better--but it wasn't because of lack of software or on-line help
principles. More help with the particulars of
writing or more experience actually writing (I don't
think the professor pushed us very hard), might have done the trick. Also,
with
what makes technical writing different than other forms of writing.
I work in software and have written articles books (book) in this field. I
still think
the difficulties are with writing--not the software process.
There has just *got* to be knowledge that's transferrable from "writing"
to technical writing.