[LarryA]

Code like a programmer, design like someone who will use it. The best approach is if you can get some test data, in order to directly experience using the system. If the user enters dates a lot, you better make the date entry method as painless as possible (no mouse popup on dates, maybe even allow for - or . as separators so operators can stay on the number pad, etc.).

Do they enter bulk records more than one-ofs then have it so they can bulk-enter a group of records, etc. If you were told to do the entry what would you want to make your life easier.

As a programmer we think of the computer and how it reacts when running our code, it also helps to think of the user and how they react when using the UI.

Of course I know a couple of the problems with this - frameworks and IDEs, some of which don't give the programmer easy access to custom interface elements (or by using such tools the programmer is never aware of other ways to implement a UI).