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.
That's talking about the documentation of the code itself, which mostly
means the code needs to be well commented.
On Fri, Mar 29, 2013 at 7:47 AM, phil stokes <philstokes03 -at- googlemail -dot- com>wrote:
> Hmm, interesting point. In one of those moments of synchronicity, I just
> happened to read an Apple doc this afternoon that ironically stated, among
> other things, that:
>
> A principal goal of object-oriented programming is to make the code you
> write as reusable as possible….Reusability is influenced by factors such as
> these:
>
> <snip>
> ***How clear the documentation is***
>
> <snip>
>
> I say "ironically" as Apple docs are about as frustrating as any docs I've
> ever read. With the exception of comprehensiveness, in any other terms,
> their work falls so far below professional standards of good technical
> writing it beggars belief.
>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>From our sponsor Doc-to-Help: Want to see a Doc-To-Help web-based Help sample with DISQUS for user commenting?
