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: What does it mean to be technical? From:"Giordano, Connie" <Connie -dot- Giordano -at- FMR -dot- COM> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Fri, 23 May 2003 11:26:26 -0400
OK everybody who's a hardware, manufacturing, or policies & procedures
technical writer... Get off the list. You're not really technical. And
that goes for all of you who never took philosophy, can't read code yet,
have vertical industry expertise, extensive background in learning theory,
journalism or marcomm!
Connie P. Giordano
Senior Technical Writer
Advisor Technology Services
A Fidelity Investments Company
704-330-2069 (w)
704-330-2350 (f)
704-957-8450 (c)
Who apparently isn't a technical writer.... Who knew?
-----Original Message-----
From: Victoria Nuttle [mailto:vnuttle -at- cauto -dot- com]
Sent: Friday, May 23, 2003 11:14 AM
To: TECHWR-L
Subject: RE: What does it mean to be technical?
>I don't need to know how to write in C# or even read C# in order to be
able to understand what the application is intended to do. I mean, what is
code, really? Is it some cryptic form of expression that takes strong
intellect to comprehend?
>No.
>It's a set of instructions designed to tell a set of circuits to do
something. That's it. Nothing more.
No. I mean yes. I mean...
Understanding code, and being "technical", is a logic thing. If you pay
attention in philosophy class and really understand how logic works, you can
look at most code and figure out how it is structured and what it does.
Every good technical writer I've known could look at any code and at the
least figure out what is happening in it.
While a good "technical" person may not be able to program in code, they
should always be able to look at all the parts and figure out how they work
together. A techie of any sort should love being able to get their hands
into the nitty gritty and figure out not just how it works, but why it
works.
--------------------------------------------
Victoria J. Nuttle
Technical Writer, Creative Automation
vnuttle -at- cauto -dot- com
---
You are currently subscribed to techwr-l as:
archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.