Difference between revisions of "Resources"
Line 1: | Line 1: | ||
{{3040Chapter|Resources=RESOURCES!.}} | {{3040Chapter|Resources=RESOURCES!.}} | ||
− | + | <p> | |
− | == Common Writing Mistakes == | + | If you're here, learning mathematics or a programming language was probably a lot easier than writing. Why is this? Because writing is an art. There is no clear line between right and wrong. If you make a mistake in your code, the compiler tells you or the program crashes. In writing, there are no guarantees a mistake in your writing will be caught in your word processor. |
+ | </p> | ||
+ | <p> | ||
+ | This chapter covers the extra tools you can use to aid and perfect your writing. The '''Resources''' section can't write your paper for you, but it can help point you in the right direction. | ||
+ | </p> | ||
+ | == [[Common Writing Mistakes]] == | ||
+ | If you're human, you make mistakes. We usually don't repeat the mistakes we make, except those that appear in our writing. Covered here are some of the more common writing mistakes in the hopes that you will be able to weed them out in your own writing. | ||
== Writing with Technology (Google Docs and Wikis) == | == Writing with Technology (Google Docs and Wikis) == | ||
Line 10: | Line 16: | ||
==== Grammar ==== | ==== Grammar ==== | ||
− | [http://www.wsu.edu/~brians/errors/ Common Writing Errors] | + | *[http://www.wsu.edu/~brians/errors/ Common Writing Errors] |
− | + | *[http://io.uwinnipeg.ca/%7Emorton/Telecourse/Academic_Writing/guide_to_sentence_structure.htm Norton's Quick & Dirty Guide to Sentence Structure] | |
− | [http://io.uwinnipeg.ca/%7Emorton/Telecourse/Academic_Writing/guide_to_sentence_structure.htm Norton's Quick & Dirty Guide to Sentence Structure] | + | *[http://www.bartleby.com/141/ Strunk's Elements of Style] |
− | + | ||
− | [http://www.bartleby.com/141/ Strunk's Elements of Style] | + | |
==== Odd/Crazy Technical Writing ==== | ==== Odd/Crazy Technical Writing ==== | ||
− | [http://poignantguide.net/ruby/ Why's (Poignant) Guide to Ruby] | + | *[http://poignantguide.net/ruby/ Why's (Poignant) Guide to Ruby] |
==== Other ==== | ==== Other ==== | ||
− | [http://www.cs.umanitoba.ca/newsite/honesty.htm Honesty Declaration] | + | *[http://www.cs.umanitoba.ca/newsite/honesty.htm Honesty Declaration] |
== Reference's == | == Reference's == | ||
− | [http://courses.cs.umanitoba.ca/index.asp?sec=3383 The Comp 3040 Website] | + | *[http://courses.cs.umanitoba.ca/index.asp?sec=3383 The Comp 3040 Website] |
Revision as of 23:10, 2 April 2008
Chapter IntroductionTechnical writers must follow a set of instructions and techniques to properly format their documents. First and most important consideration is the overall document layout. Documents should be designed in a way that would allow the reader to effectively reference key points and enhance the decision making process. The component layout should enhance or maintain reader's interest in you document. Proper use of definitions and descriptions ensures that your audience can follow along and are not facing ambiguities. Documents may be used directly by technical personnel to perform their job, therefore it is essential to provide detailed documentation for their operations. Finally, graphical content techniques can be employed to enhance the data presentation and analysis.
|
If you're here, learning mathematics or a programming language was probably a lot easier than writing. Why is this? Because writing is an art. There is no clear line between right and wrong. If you make a mistake in your code, the compiler tells you or the program crashes. In writing, there are no guarantees a mistake in your writing will be caught in your word processor.
This chapter covers the extra tools you can use to aid and perfect your writing. The Resources section can't write your paper for you, but it can help point you in the right direction.
Common Writing Mistakes
If you're human, you make mistakes. We usually don't repeat the mistakes we make, except those that appear in our writing. Covered here are some of the more common writing mistakes in the hopes that you will be able to weed them out in your own writing.