Technical writing philosophy, sample, availability

Note to readers: Clearly this is a work in progress. I will be addressing the issue of technical writing philosophy among other issues. In the interim, you might find the following link helpful: http://www.joelsolkoff.com/my-experience-as-a-technical-writer/

Currently, l am writing documentation for a complicated electrical mobility tool. Ever since 1990, when my family and I relocated to the Research Triangle area of North Carolina, I have written documentation on a regular basis working for such companies as Nortel Networks, IBM, Schlumberger/Sema, and three start-ups in the Silicon Valley (a place where my heart resides).

[youtube]https://www.youtube.com/watch?v=YQy0ZCx3UCY#t=32[/youtube]

The following example dates from 1995, one of the most difficult years of my life. Certainly, I would not have made public any document that is classified (as is the one below) if time did not make such classification moot.

What makes this sample useful is that it represents, as I will discuss, the best example of an optimal organizational structure to produce documentation. Since writing, KLA has merged with Tancor. I will always be grateful to KLA-Tancor for making possible the production of quality documentation unequaled by subsequent experience.

KLACover

WaferMaps

 

 

8-2

 

 

 

8-3

 

8-4

 

 

8-5

 

 

8-6

 

 

 

 

 

 

 

8-7

 

8-8

 

 

 

8-9

 

 

 

backcover

 

klamanual

Leave a Reply

Your email address will not be published.

This site uses Akismet to reduce spam. Learn how your comment data is processed.