>>>Absolutely. I mean that we should develop system assuming that at the end client will look at this and will be compelled to ask at least something. For example, I never add "Are you sure ..." messagebox in cmdSave.Click just because I know that client will ask for this later and I will be able to make him happy easily enough. Basically, it's all fringes, that could and should be added (or not) when real development cycle is over. That's the one practical difference between robust and sloppy design. The former one allows to add fringes easily, and the latter one not.
>>
>>I went to one of Jim Booth's sessions about user design and Programmers make the mistake of designing the way the programmer wants to see the program. Often times this is not the way the user wants to see the program. Time and time again, I have seen time wasted on really "cool" features that the user has no desire for.
>
>Yes, but basically development is not about users, it's about database design, application hierarchy, foundation classes etc. Users don't know and should not know about these things and it's completely up to developer to decide what to do here. Users want an application to automate some business process, work smootly and take minimum of maintenance efforts, that's it.

For the most part yes. I've had user's ask for some pretty bizarre behaviors. Things I would never include or even offer as a feature until the user says, "Hey, can you make it so it will brush my teeth when I press this button?"