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.
Dave,
I did some API documentation for a while a few years ago. For that job they mostly required that I be able to read and understand the code so I could pull out samples to put in the documentation. When I applied for the job I made it absolutely clear that although I could read code and understand it for the most part, there was no way I could ever write code, even for samples. They were fine with that, and as it turned out, my ability to read the code was enough.
I would guess that the fact that you you can write C--even though it is very different than C++--will serve you well in an API doc job. You will have better than average skills at looking at the C++ and being able to pull samples from it by virtue of the fact that you can write code in another language.
