3 ms·
As a 'programmer' I find I often have a better idea than end users about what should be implemented. I sit in front of the system I am building all day, and I n
by collyw 11y ago
As a 'programmer' I find I often have a better idea than end users about what should be implemented. I sit in front of the system I am building all day, and I notice if performing certain actions is too slow or frustrating. I take an interest in UX concepts and will read articles on them, as opposed to "can we get a new button here to do X" without any real thought going into the process.
- dfox 11y agoThat assumes that you as a programmer actually use the thing you are building for something else than testing. I've seen many LoB applications that get optimized by this process for programmer testing instead of normal user workflow. Yesterday's example (the application is desktop thick client for REST web service): (mostly developmen only) UI for manually creating test data is readily available on application's toolbar, while button for reloading form/view state from server has different placement on each form and in some parts of the application is completely absent (obviously, UI programmers restart the thing often enough that they essentially don't need that button).
- dagw 11y agoThat only works if you work on apps that you actually use, and more importantly use in the same way that your end users use it. Having worked on specialized engineering applications where I'm not the end user, I'll admit to on more than one occasion making some really stupid UX decisions since it turns out that the engineers actually working with the app on real projects where using it very differently than I was when testing it on a tiny made up toy project. Spending just 20 minutes sitting next to someone trying to get real work done can be a real eye opener some times.
- collyw 11y agoI watched the users of my last app cut and paste data from the application into excel, mess with the data in excel, upload the excel back to the database and ask me what was causing the errors when the unvalidated data in excel would not go back in to the DB. It was eye opening how they accept such a crap system. I tried to change it, but it was never given high enough priority.
- bitwize 11y agoWell, then, it's your responsibility to make sure that your application can cope with data pasted in from Excel, since that's obviously a critical part of the users' workflow.
- collyw 11y agoIt was a "temporary solution". "Yes, you can built a web form with proper validation to replace it next month after you complete this URGENT feature". If it can be replaced by a web form then Excel isn't a "critical part of the workflow". Getting data into the database was the critical part of the workflow. The users actually preferred the web forms that I did manage to replace Excel sheets with (more checkboxes, and far less cut and paste). Anyway after 3 years of complaining about the same issues I realised it was time to leave.
- chippy 11y agoin other words "Don't program like a designer"
- emodendroket 11y agoWell, yeah, I don't think anybody thinks handing off design decisions to end users is a good idea.