3rd Indiv Post- Comments on Jack Johnston’s Individual post, Jack and Alan’s collaborative post, and Cathie and Emma’s collaborative post
Jacks Individual Post
1st Reading- I agree with Jack, but I would add that the article not only stressed how technical writing could be important in a job with a rapidly change in technology, but in fact all jobs.
2nd Reading- From the article, I did not get the impression that they deal “a lot” with instruction manuals, although I agree they definitely write them. I think that they deal with the manuals as much as they do anything else.
4th Reading- I like the point he brought up about “A confused audience is just as good as no audience.” I think that this is a very interesting and good point. If your audience cannot understand what you are saying, why are they sitting there wasting your time and theirs?
Overall, I enjoyed his views on the reading and found them helpful.
Jack and Alan’s Collaborative Post
When they say the “easiest form possible,” I believe this point could be expanded upon and some examples given. I think that this does not necessarily mean word form, but graphs, charts and pictures in general but I am not sure from this particular phrasing. I have done a few power point slides for my work in which I had one slide of bullet points and about 20-25 slides of pictures and I was told “you have too many words in the power point. Remember, a picture is worth a thousand words.”
Jack and Alan make an excellent point in saying, “The difference in proper and improper technical writing could be the difference in the saving of a life and the unexpected loss of life.” I had said it before, but I have seen videos of bridges falling apart and satellites falling to earth due to improper technical writing and communication.
Great collaborative post.
Cathie and Emma’s Collaborative Post
In this post, Cathie and Emma say that the article may contain “subject specific jargon,” which could be true, but I would also add that the writer must be careful of his audience if he uses jargon specific to the subject. For instance, the author could be referring to a machine that non-technical people work on, but his / her audience is a group of engineers. The author could certainly use jargon specific to the machine and be completely correct in doing so; however, this could potentially be problematic should audience of engineers not know the operators’ terms and word usage.
Cathie and Emma also say that “its purpose is to convey, thoroughly but briefly, exact information and/or instructions.” I completely agree with this sentence because in many articles, authors talk about how important it is to be brief and concise in technical writing.
Another great post.
1st Reading- I agree with Jack, but I would add that the article not only stressed how technical writing could be important in a job with a rapidly change in technology, but in fact all jobs.
2nd Reading- From the article, I did not get the impression that they deal “a lot” with instruction manuals, although I agree they definitely write them. I think that they deal with the manuals as much as they do anything else.
4th Reading- I like the point he brought up about “A confused audience is just as good as no audience.” I think that this is a very interesting and good point. If your audience cannot understand what you are saying, why are they sitting there wasting your time and theirs?
Overall, I enjoyed his views on the reading and found them helpful.
Jack and Alan’s Collaborative Post
When they say the “easiest form possible,” I believe this point could be expanded upon and some examples given. I think that this does not necessarily mean word form, but graphs, charts and pictures in general but I am not sure from this particular phrasing. I have done a few power point slides for my work in which I had one slide of bullet points and about 20-25 slides of pictures and I was told “you have too many words in the power point. Remember, a picture is worth a thousand words.”
Jack and Alan make an excellent point in saying, “The difference in proper and improper technical writing could be the difference in the saving of a life and the unexpected loss of life.” I had said it before, but I have seen videos of bridges falling apart and satellites falling to earth due to improper technical writing and communication.
Great collaborative post.
Cathie and Emma’s Collaborative Post
In this post, Cathie and Emma say that the article may contain “subject specific jargon,” which could be true, but I would also add that the writer must be careful of his audience if he uses jargon specific to the subject. For instance, the author could be referring to a machine that non-technical people work on, but his / her audience is a group of engineers. The author could certainly use jargon specific to the machine and be completely correct in doing so; however, this could potentially be problematic should audience of engineers not know the operators’ terms and word usage.
Cathie and Emma also say that “its purpose is to convey, thoroughly but briefly, exact information and/or instructions.” I completely agree with this sentence because in many articles, authors talk about how important it is to be brief and concise in technical writing.
Another great post.
posted by David Floyd at 5/30/2008 07:57:00 PM
0 Comments:
Post a Comment
<< Home