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: FW: New TECHWR-L Poll Quest From:"Wally Glassett" <wallyg99 -at- home -dot- net> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Tue, 12 Dec 2000 08:41:55 -0800
Asking a developer if they are knowledgeable about some function or
technique in some language tends to be a more specific question that should
have a specific response/answer, as compared to asking how one would do a
document. I am usually asked how I would go about producing a document, and
I think that's fair game because I can describe the processes I normally use
to gather and organize the information/content, as well as
techniques/approaches to presenting that information. IMO, discussing that,
along with reviewing my samples, constitutes a fair and reasonable "test" of
whether I know what I'm doing or not.
However, I have virtually no idea how often, or if, developers are asked to
write code during interviews, or if they bring "portfolios" of code samples
with them to interviews.
Any input(s) from the developers out there?
Tech Doc-It, Inc.
wallyg99 -at- home -dot- net <mailto:wallyg99 -at- home -dot- net>
Damien's and others' answers indicate that developers often get tested for
proficiency--which makes me wonder why so many tech writers are offended by
writing tests. If the development staff takes some sort of test to prove
their proficiency, what makes writers so special? And no, I don't mean "how
to tie a shoe" type tests. I mean tests that show ability to grasp the
overall concept of the product, write some basic procedural and conceptual
information, and ask questions that demonstrate curiosity.
Take XML and Tech Writing courses online! Our instructor-led courses
(4-6 hrs/wk) give you "hands on" experience at your convenience. STC members
get 20% off! http://www.online-learning.com/index.html.
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.