**Chapter 1 Reflection**
I liked that Chapter 1, “Introduction to Technical Communication,” made the point
that technical communication isn’t just about writing complicated information. It is
about presenting information clearly, usefully and appropriately to the reader. The
title “What Is Technical Communication?” made me think more carefully about the
amount of communication that takes place in technical fields, even outside of long
reports. For example, the writer needs to know the audience and the purpose when
writing emails, instructions, proposals, and presentations. I also liked the way the
chapter connects technical communication to real world workplace scenarios. This
made the reading feel useful, not merely academic. In my future job I will probably
have to teach technical information to people who might not have the same
background as me. This chapter has made me understand that good technical
writing is based on clarity, organization and responsibility.
**Chapter 3: Reflection**
“Writing Technical Documents” (Chapter 3) The most interesting proposition in
Chapter 3 is that writing is a process. The chapter divides the process into Planning,
Drafting, Revising, Editing, and Proofreading. I liked this because it shows that good
technical documents usually don’t happen in one step. Planning is important as it
allows the writer to understand the topic, audience, purpose, schedule and needed
research before beginning. It also helped me to know the diRerence between
revising and proofreading. Revising is more about refining the ideas, organization,
and usefulness of the document . Proofreading is more about correcting smaller
errors . This is important because a document may be grammatically correct but
confusing or poorly organized. Overall, this chapter helped me to realize that
technical writing requires patience and thorough attention to the needs of the
reader.
**Chapter 4 Reflection**
What I liked about Chapter 4, “Writing Collaboratively,” is how realistic it is about
group work. The chapter has “Advantages and Disadvantages of Collaboration” and
this stood out to me because collaboration can be helpful but also hard. A group
can make a better document because people have diRerent ideas, skills, and
perspectives. But if people don’t communicate well, divide the work fairly or meet
deadlines, working together can cause problems. The sections on meetings,
listening and communicating diplomatically were also helpful. Many classes and
jobs require group projects so it is a good skill to have to work well with others. This
chapter taught me that collaboration is not just putting everybody’s work together. It
takes planning, respect, feedback and shared responsibility.
What do you think dudes?
What do you think is the most important skill in technical communication: knowing
your audience, using the writing process, or working with others? Why?