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.
-----Original Message-----
From: Bill Swallow [mailto:techcommdood -at- gmail -dot- com]
Sent: Thursday, November 03, 2011 10:24 AM
Subject: Re: Career|Skill Advice
>>
I'd go one step further and say once you can understand code, you need to know what to do with it. Should you be able to create sample applications? If you're documenting APIs and SDKs, then ideally that answer is "yes".
>>
Perhaps I should have said "Should anyone expect you to be able to create an application in the same time as the programmers you work with? No. But should you still be able to do it, given enough time? Yes."
No one should expect you to do the work of an actual programmer all the time (if they do, change your job title and look for a job that pays an engineering salary) but you should be able to complete a sample application.
- V
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Create and publish documentation through multiple channels with Doc-To-Help.
Choose your authoring formats and get any output you may need. Try
Doc-To-Help, now with MS SharePoint integration, free for 30-days. http://www.doctohelp.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-
