|
-
May 23rd, 2004, 10:43 AM
#1
Thread Starter
Frenzied Member
User idiocy
In general, how much of your coding is designed for breaking code?
I don't mean catching exceptions, but designing for user errors. We can all design for correct users, but I don't find them very often.
For instance, some employees at my firm use Access to manipulate data. They do so with an Access form that basically presents them with the table they're working on.
They have no problem doing this. But when I show them that they can open the actual table (which is all the macro (ugh!) does when they click a button), they're lost.
I seem to spend a lot of my time dumbing down apps, at least the gui, to accomodate the user.
I guess in some way, this has to be done. But I'm in a situation where I can make incremental improvements to an existing, aging but working system, or redesign the whole system to a better model, with inevitable bugs to be worked out. What's your opinon?
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|