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.
I am the only techwriter doing end-user docs, and the company wants
someone to document code. I'm supposed to interview the applicants, but
they've asked me whether I'd consider doing it.
What would you look for, since our company has a product written in C,
some new code in C++ (with some APIs in the pipeline), and Visual Basic?
I'm learning VB and have coded a little (Basic and Fortran) myself but
never documented code. Would it be better for me to learn on the job,
since most of our applicants want to do end-user documentation, or is it
too hard to learn on the job? What questions do I need to ask of
management?
Sorry to ask several far-ranging questions, but that's what's going on!
