PeterN
On 12/4/2013 5:43 PM, nospam wrote:

nospam
In article <bp9v99p9gj3bd48h7u8uesjr1p02n02o5s@4ax.com>, Eric Stevens <eric.stevens@sum.co.nz>wrote:

Sandman
And your followup question is totally unrelated to this. A race car driver can have their car "set up differently" to suit their preferences without knowing the first thing about car mechanics (and especially ENGINEERING) since they are part of a race team where there are actual mechanics that will adjust whatever needs adjusting, and would do a far better job than if the driver did it himself.

Eric Stevens
How do you think they know what needs adjusting? They know because the driver tells them. There will be discussion over the details (as no adjustment affects only one aspect of the car's performance) but the top drivers have major technical input.

nospam
they can report the symptoms they encountered and offer input as to how the car is performing. drivers do that every day when they bring a car in for service.

however, they don't need to know how to fix the car or tune it to perform the way they want. that's for the mechanics to do.

PeterN
It's hard to agree, less. While you don't have to know how to design and build a car, you can save an lot of money, if you have a basic understanding of the principals that make it work. e.g. On my station car the remote start stopped working and the cruise control wold not stay on. the mechanic was ringing the register, as he suggested what "had to be done." I asked him to test the battery, since I figured the common denominator waas an electrical problem. Bingo!

Eric Stevens
Because you didn't say the architect could do well to understand the basics of computing.

Sandman
That's not an answer to my question. Me not saying that is not the same as me saying that the "Programmer leads the way". You have a reading disorder. Maybe dyslexia? Maybe ADHD? I don't know, but you clearly can't read English.

Eric Stevens
The problem is that you have a narrow understanding. It's up to the architect to decide where he wants to. It's the programmer who has to take him. This only works if the architect has some understanding of what is possible.

nospam
he doesn't need to know what's possible and it's probably better if he doesn't.

he might think something is not possible and then not ask for it, not realizing that someone who knows more than he does can do it and might even have already done it in another project.

i've seen that happen a lot.