Len are you suggesting that trial and error is not a valid option.?
Brian
Not at all but I think it is important to understand where the trial and error bit actually occurs.
So you have a task to perform, some sort of in depth analysis that you heve never done before then the determination of the process required is not trial and error really it is the disection of the problem and the building of a logical process concept.
Next process it to consider the process concept and resolve this into something more approaching say a chunk of code. At this stage pseudo-english probably with a bit of actual code for variable declaration and loops.
Only now does the trial and error bit maybe start to happen. This is when you are writing say SQL within VB all within various loops. getting the synatx correct can be a bit if a nightmare (for me anyway) and ensuring that the code is actually doing what you intend. Making sure there is not a logical error for instance. Even here the trial and error does involve the logical analysis of the result, be it error message or data.
So Trial and Error does come into the equation but I do not think that the initial analysis, disection, process concept and realisation phases should all be lumped as Trial and Error.
Monkeys (real ones) writing code would produce the result by trial and error eventually (XXXX years). We (most anyway) are capable of very high logical thought processes and these are not trial and error. (in my opinion anyway)
Writing a bit of code to extract data and then determining if this is actually what the user wants is not trial and error. It is the User not specifying what they want which is quite common I have found.
Finally I think that useing a skill to test a scenario is not really trial and error and final finally if we did admit to trial and error then it is not a strong basis from which to debate the next salary increase.
Bit of a ramble bit hope I have explained myself
Len