>Robert Edmonds wrote:
>>
>>  Here's another benefit I see from certifications like this:
>>  there are
>>  things that all of us know how to do, but if asked to walk
>>  someone through
>>  it over the phone, couldn't do it.  For example, for me it
>>  would be DNS
>>  configuration.  I can do it, but I can't tell YOU how to do
>>  it.  I know it
>>  just well enough to kind of stumble through it and get it
>>  working.  And I
>>  can get it working CORRECTLY.  It's just that I am weak in that
>>  area.  With
>>  a performance based test in a lab situation, I could pass by
>>  getting it to
>>  work, but I may not be able to answer the question correctly on
>>  paper.  And,
>>  in my opinion, it's more important to be able to "walk the
>>  walk" than "talk
>>  the talk".  What do you think?
>
>Talking the talk is very important too. Think proactively. Hopefully, before
>long, you'll be moving up in the world. If you can train your replacement to
>do what you did, then you can move up with fewer impediments. If you can't
>train a replacement, then you may not be able to move up, or you may move up
>and continually get calls from your replacement asking for your help.

Increasingly, I like my conceit of talking the walk. Talking the talk 
may be more characteristic of sales. Remember, some of the important 
distinctions between a seller of used cars and an account executive 
for networking are that the seller of used cars both knows when he is 
lying and how to drive.

Walking the talk also makes more sense -- it is the ability to listen 
and learn, and can be generalized to researching who has talked about 
what.

>
>
>I have worked with engineers who have never given any thought to learning,
>training, etc. You know the type who can only work with concrete things and
>considers any social science like education or psychology to be hogwash. ;-)

Were it not for social sciences like anthropology, you and I couldn't 
be tribal elders or shamans.

>These types get stuck doing all sorts of mundane things that are beneath
>them because they can't explain to someone else how to do it. This probably
>doesn't apply to you, but it's just something to think about.
>
>It's funny that you use DNS as an example. I'm working with an engineer
>right now who has said he will show me his DNS tasks but he has failed to do
>this. I wonder if it's because he only does it once in a while and is afraid
>that he won't be able to explain it to me. I'll try to go easy on him, now
>that you have helped me see his side of the story. :-)
>
>Priscilla




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=54570&t=54435
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

Reply via email to