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.
>Calling programmers engineers is a slap in the face, IMHO. Call us
>developers or programmers, but don't call me Susan.
I don't know about the Susan part, but during most of the fifteen years I
spent as a programmer I shared that view of engineers -- an attitude that
carried over from my years as a mathematics student at RPI, a second-tier
engineering school in those days.
I still think of myself as a programmer at heart, but I no longer think
that programming is more about art and communication than it is about
engineering. Certainly not as it's practiced at the large software
companies today.
And I no longer think that technical communication is more about art and
communication than it is about engineering. It is an engineering
discipline
-- just like making microchips, computers, or software. ...RM
Richard Mateosian <srm -at- cyberpass -dot- net>
Review Editor, IEEE Micro Berkeley, CA
