Amen, brother

>>In my experience, the client generally doesn't give you time to do nifty interfaces anyway....they want the job done....there are those in our profession who have garnered bad reps by being too slow to deliver when trying to perfect an interface.
>
>This goes along with a comment you've made in the post about 'should you use a Save Button?' I your comment with respect to enterprise data integrity was along the lines of, my resposibilty for the client is to protect the data, not to provide a slick interface to the data for the clients employee.
>
>This and the above bring a touch of realitly into our little worlds. There is a strong economic force behind a lot of software developemnt. This taints our idea of development theory. If we had more time GREAT. But the real world has its own constraints.
>
>I often wounder what state computers and software would be in today if they were deveolped by theory and economics was not a factor. But I've got to admit, it's economics that have driven the PC to its current state.
>
>>I guess I have the same aversion to blind adherence to an interface *theory* as I do to blind adherence to OOP theory....compromises and the purpose of the application *have* to be considered.
>
>I agree. Blind adherence to anything is dangerous. Never forget your context.
>
>Later