>>But we know how to build software, the client doesn't.

That point is debateable.


>
Did you see the Simpsons where Homer's brother let Homer design his very own car 'for the people'? The result was analagous to what I think you'd get if you allowed the client to completely dictate the UI choices for you app, and gave them no guidance along the way.
<

Yes. Danny Devito was the voice of Homer's Brother. As for what happens if you allow a client to dictate UI choices, you may or may not have problems. Sometimes, the simple approach works. Again, over-thinking the issue can run into problems. Often, the best ideas come from clients.

I tend not to take an overally arrogant view of what a client knows/does not know. I do tend to get ticked at those who put themselves up to be something they are not.

To say we know how to build software, the client does not to me borders on arrogance. The issue only matters if the client needed to know how to build software. The fact is, the client does not need to know. Therefore, what does it mean that a client does not know how to build software?

The question is whether the "alleged" software developer knows how to build software - correctly. The fact is, the vast majority of development is done by trial and error. The vast majority of software developers have very little discipline, put forth very little in the way of design and analysis. I have seen too much crap code in my career and have seen and bailed out far too many failed projects to think otherwise.

I have met some truly gifted people in this business. Sadly,they are the exception, not the rule.

The best of the best can both articulate the theory and put it into practice. I have seen and heard great theorists who have little to show for in the real world as far as real applications are concerned. And, I have seen people crank out code faster than anybody to get something up and running. However, what was cranked out is far from optimal as far as design goes. The best of course, fit right in the middle. They don't let theory get in the way of delivery. At the same time, the don't let delivery compromise good solid design.

It is a balancing act that only a very very few have mastered.

< JVP >