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: Do you equate engineers and programmers? From:LaVonna Funkhouser <lffunkhouser -at- HALNET -dot- COM> Date:Thu, 18 Aug 1994 18:07:03 -0500
*Warning, I am venting my anti-engineer-as-programmer
bias.*
Gwen,
Thanks for the engineer bashing! I didn't say this
in my original message because it wasn't my original point,
but you are exactly describing what goes on here!
When an engineer decides to take on a programming job himself,
management views the product as a masterpiece, but the software
guys that get stuck working with it later go nuts over the
lack of structure! (Even *I* took a course in Data Structures;
how many engineers where I work can say that?!)
One math genius (I mean that) who was recently laid off was known
for writing spaghetti code, but it made perfect sense to him. He
could always find the offending line when nobody else could.
I guess I'll stop at that. I've already stated that I'm biased so
you have to take that into consideration.
LaVonna
lffunkhouser -at- halnet -dot- com
disclaimer: This does not reflect the opinion of my employer!
