Today I was reading some documentation on OER. I found the particular document very hard to comprehend. The I got to thinking, “It’s not so bad.” I mean, at least it’s written in my native language. Even when I take Cisco Exams I know that I have a slight advantage because it’s written in my native language. But I think that sometimes people in the United States may overlook this issue. You see, not everyone that takes Cisco exams, or other vendor exams for that matter, are native English speakers, and not all exams are written in languages ”other” than english. This may put non-english speakers at a disadvantage. So todays tip is related to reading comprehension. If one doesn’t understand the question then how can they be expected to answer? Well, as far as most vendors are concerned: That’s your problem. You are expected to understand the question- so figure it out. Easy enough right? Not really. So this post is dedicated to those who are having a hard time with things. So you are probably wondering, where can I find assistance in comprehension?
Sources of Assistance
If you are in the networking industry then its likely you already know how to search Google. If not, give it a try. I’m not kidding. Some people still do not use google. But let me tell you, It can work wonders. Now, don’t get me wrong- I’m not talking down to any one. There are things that I do NOT comprehend. It’s normal. So you may have to dig deep for the answers. In the information age, the answer is likely there. Make an effort to go a few pages into the search results if you haven’t found the answer yet.
Social Networks
Don’t stop at a single search. Use Social Media. Post a question to Twitter, Facebook, Cisco Learning Network, and so on. Community sites can help. Granted, you are going to find people that will reply in a snide manner, but don’t let that get you down. Most people want to help and they will. Just be humble when you ask your question.
Technical Documentation
You’ll find that Technical Documentation may be the most difficult documentation to read. You’re probably correct. Most people are not trained to write technical documentation and therefore it is not clear and precise. Also, there is so much to cover in single-document type material that the wording is bound to trip you up. Just do the following:
- Read the statement that does not make sense.
- Considering the context that the statement is in try to relate it to the task at hand
- If the question still does not make sense then refer back to the fist and second heading of this post
- If you have the ability then try to test the concept in a lab (In my opinion, hands-on is the best way to learn something in.)
Other Methods
Take a Class. That’s right, I said it. You may need training. Training can sometimes be found for free. Again- do an internet search and you’ll be amazed at the results that are returned.
Technical Understanding
One last tip I wanted to mention is the Internet Technology Handbook. If you haven’t spent some time reading it and you are new to networking it may prove to be helpful. The terminology used here is generally accepted as the norm. So being familiar with it, and the way things are worded can help. Take the time to look up any words you don’t understand. In time your comprehension will improve and the test taking process will become easier than when you started.
Well that’s the tip for the day. Thanks for visiting and be sure to share the article with your friends and colleagues. If you have any additional tips or requests why not leave a comment?
Great tips Brandon. It always amazes me as to how many people still don’t use google when trying to find something out…I mean I use it for almost everything, not just technical. I wanted to know how to make papas rellanos (those meat stuffed potatos that Armine brought to our class) and I found tons of sites on google of how to cook them. That just being an example that there is no limit to the resources you can find there. I do find technical books difficult unless I have a specific topic that I really need to learn, reading straight through a 1000+ page technical book is rarely ever how I study.