![]() |
|||||
|
Chris Wednesday |
Wednesday Write New Feature Documentation
Soon I have everything I need to get started writing. I find a perfect place for this new content in the user manual. I think about what chapter title and section headings best communicate my information. I decide to use gerunds as headings, which inform readers what they will learn or accomplish in the chapter. This design is one component of the task-based approach to documentation. I begin the chapter with just enough background material to put the feature in context. For more information, I reference a well-known textbook the developer told me about. After that, I include a tutorial that introduces several key terms and ideas. From there, I discuss how the feature works. Because customers can use LabVIEW in so many different ways, I can't anticipate exactly what a customer will need from the documentation. I want to provide our customers with as much information as possible. After I finish the first draft, I put it aside and work on other projects for a little while before proofreading. It's always a good idea to put some mental distance between draft revisions. Doing so gives your brain a chance to process what you've just written. Volunteer at Shoes for Austin
Attend a Brown-Bag Presentation This afternoon I attend the brown-bag presentation that Robin and Neerja put together. They talked about our department's recruiting efforts and how people can get involved. Even though I'm fairly new to the company, I still want to get involved with recruiting other technical writers. Recruiting seems like a fun way to meet new people and take on new responsibilities at the same time. At some point I will join a recruiting team, most likely the one that goes to the University of Texas, and meet with other team members on how to attract and evaluate the best technical writer candidates. |
||||
|
|||||
© 2006—2010National Instruments Corporation. All rights reserved. About This Site | Opportunities at NI |
|||||