Technical Communication, by definition, helps us interact with technology in our daily lives. The most common forms of technical communication come from the installation instructions for your brand new gadget, to the menu on an ATM, or a Google search for a “how-to” on the newest software you’ve just downloaded. During our everyday lives technical communication is common all over, even in the workplace. I would say more so than anywhere else. But that’s also my opinion. I think it is important to give examples on the subject because of its broad base. Some specialized questions and situations, quoted from the book, where technical communication is necessary include:
“A government research scientist must have accurate instructions about how to write a grant or how to perform a particular experiment”
“An engineer must have access to the correct specifications for designing a bridge or configuring a software application.”
“What are the technical limits to wind energy?”
These are just a few examples. It sounds to me like a lot of confusing scenarios boiled down to one thing. Whenever someone may need instruction or guidance for a task beyond their understanding involving technology, technical communication is needed. It could be the newest internet service provider’s security system or a setting on your washing machine at home.
No comments:
Post a Comment