Writing Better Technical Reports
Technical reports require attention to sentence, paragraph, and document structure. They also demand careful word choice, avoidance of ambiguity, proper treatment of jargon, and awareness of style issues. This course shows how to be a better writer.
What you'll learn
Technical professionals must occasionally write technical reports. Although there is no one right method for doing so, certain techniques and methods usually improve the results. In this course, Writing Better Technical Reports, you'll be encapsulated with a wide-ranging discussion of structure and style into successfully writing technical reports. First, you'll learn many of the more common writing mistakes and discover techniques for avoiding them. Next, you'll delve into a reader-oriented approach that will improve your reports' reception and effectiveness. Matters of sentence, paragraph, and document structure receive consideration here, along with tone, ambiguity, and technical jargon. Additionally, you'll explore tips specific for electronic document formats. Finally, you'll cover techniques for joining paragraphs using transitions, facilitating navigation within the report, avoiding confusing or opaque references, and exorcising bad habits, such as redundant, superfluous, and imprecise verbiage. By the end of this course, you'll have a solid understanding of how to efficiently make your technical reports leaner and more readable.
Table of contents
About the author
Glenn E. Weadock (MDAA, MCAAA, MCT, MCSE, MCSA, MCITP, A+, Security+) is the president of Independent Software Inc., which he founded in 1982 after graduating from Stanford University's engineering school. ISI provides expert witness, consulting, and training services in the IT field with a focus on operating systems and networking technologies. Glenn is the author of 18 commercial books on topics such as Windows clients and servers, Microsoft certification, website design, troubleshooting, and ... more