4 ms·
Talk about an unambiguous sign that whoever is writing this software is truly and deeply giving zero (0) shits about their job.
by jfb 14y ago
Talk about an unambiguous sign that whoever is writing this software is truly and deeply giving zero (0) shits about their job.
- igul222 14y agoI don't think that's the case. It's very possible to be a good programmer and care deeply about your work, but at the same time be a terrible UX designer. Unfortunately a lot of software companies don't realize this and give UX the priority it deserves; instead they make their coders guess about it, which leads to things like this dialog.
- jfb 14y agoOh sure, I'm a living disaster area at UX. I meant more that whoever is the "designated responsible individual" (if one even exists -- doubtful) has given the fuck up.
- evincarofautumn 14y agoFor some reason I didn’t read “the fuck” as emphasis, but as a direct object—the person had had a fuck previously, but have since given up that fuck. I’m going to use that as an example of why UX is hard: not only are people generally not paying attention, but sometimes they misfire even when they are.
- jfb 14y agoIt's much more elegant in your reading.
- wmf 14y agoThe basics of UX design can be learned, so if you really care you'll learn.
- Alterlife 14y agoOr, the error message was written by someone whose first language is not English... and the company in question did not enforce review.
- chii 14y agoor even that the message makes perfet sense to the person writing it, because they are not reading the message, but reading what they thought the message was in their head!
- B-Con 14y agoOr maybe the backend code is analogous to bool exit_handler(obj) { return confirm_exit(obj->description) } and he simply missed the unfortunate dialog box that resulted in one of those cases. An oversight, but when the subtitles of the user presentation is so decoupled from the code it can be easy to miss.