[Fury]

I've probably read some of their handiwork in some recent documentation I've reviewed. I believe in many cases, it takes someone who has grown up in a society to explain how to use certain products. Sometimes, the different cultures clash when attempting to communicate, as *how* they do the communicating is the key.

A good example is Tech Support. The accent of some engineers is so difficult to understand that I've had to on occasion ask to speak to another engineer and I've given the reason as "I can't understand what you are saying because your accent is so pronounced".

[harpseal]

I've probably read some of their handiwork in some recent documentation I've reviewed. I believe in many cases, it takes someone who has grown up in a society to explain how to use certain products. Sometimes, the different cultures clash when attempting to communicate, as *how* they do the communicating is the key.

Most people think the primary job of the programmer is pushing bits. The primary job of the programmer is understanding what the program is supposed to do and making it do that.

The actual code is usually the simplest part of the job.

A good example is Tech Support. The accent of some engineers is so difficult to understand that I've had to on occasion ask to speak to another engineer and I've given the reason as "I can't understand what you are saying because your accent is so pronounced".

If you as a user can not understand tech support that person you can not understand is effectively useless and not at all productive.