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: API doc question From:Chris Despopoulos <despopoulos_chriss -at- yahoo -dot- com> To:techwr-l -at- lists -dot- techwr-l -dot- com Date:Fri, 5 Mar 2010 05:29:25 -0800 (PST)
It sounds like you have lots to be proud of. If you had answered that question the way you described your API docs here, who knows... Maybe you would have gotten the job and maybe not, but you would feel certainly differently about the interview. It sounds like you rose to the challenge and delivered in spades. That alone shows a host of marketable skills.
I suggest, if you have the spare time, you go back and think over this project so you can describe it in as much detail as you need for the moment. The project shows that you can and do learn what you're writing about, and you can and do implement solutions to problems. That's valuable whether you're writing API docs or not. (And I've inherited too many projects that showed neither on the part of the previous writer.)
Probably your biggest strike against you for API docs is how long ago you did this. API writing has matured, and thinking about what to deliver has evolved. If you want to work as an API writer, I suggest you dig in and use some different APIs. Your past work was pretty low-level -- Java packages. That's good, in my opinion. Maybe you should get Eclipse and some Java tutorials, and get familiar with developing. Java's not too daunting (easier than C++), and much of the language is an assembly of different APIs. There you go. Or you could dig into Google's web APIs and see how it works for these. And while you do it, think critically about the docs. Do they really help? How much of your learning is related to the API vs your need to learn about the underlying technology? How much should the docs cover the underlying technology?
Anyway, good luck. I guess this is a lesson learned -- value your past work, and keep it handy in your pocket. In this case, your work was pretty darned valuable!
Use Doc-To-Help's XML-based editor, Microsoft Word, or HTML and
produce desktop, Web, or print deliverables. Just write (or import)
and Doc-To-Help does the rest. Free trial: http://www.doctohelp.com
Explore CAREER options and paths related to Technical Writing,
learn to create SOFTWARE REQUIREMENTS documents, and
get tips on FUNCTIONAL SPECIFICATION best practices. Free at: http://www.ModernAnalyst.com
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-