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:Engineering Writing vs. Technical Writing From:Michael Johnson <michaelj -at- OECMED -dot- COM> Date:Wed, 25 Mar 1998 12:30:40 -0700
I have found most hardware and software engineers to be an incredibly hard-working, hard-thinking bunch. When they do find time to write (which isn't often enough) they produce really dense, meaty stuff that their peers readily understand, but often sails over the head of a worst-case technician like myself.
It's my job to massage this Engineering Writing into Technical Writing that users and maintainers of hardware/software systems can understand.
And, believe it or not, inventing that communication is really a lot of fun and a super cool way to learn new stuff.
No, I didn't just swallow a bottle of Prozac. I'm just having a good day. Hope you are too.
Mike Johnson
OEC Medical Systems
Salt Lake City, Utah
Michaelj -at- oecmed -dot- com
Writer -at- wasatch -dot- com
