3 ms·

>Never-Ending Learning of User Interfaces At first I thought it's about users continually being forced to relearn UX they relied for years because app's develo

>Never-Ending Learning of User Interfaces At first I thought it's about users continually being forced to relearn UX they relied for years because app's developers came up with a new "design" that should "improve things" according to their "studies" which found something confusing.

deleted 3y ago
[deleted]
luckman212 3y ago
That's what it should be about. I thought the same thing. I'm so tired of looking for where the "submit" button is or trying to figure out your stupid new password requirements. Must contain: 1 letter, 1 emoji, 2 uppercase, no "Z"s allowed... smfh
- eddd-ddde 3y ago
  You forgot to include today's wordle answer in your password.
analog31 3y ago
This is why the number-one request from users is: "Please don't change anything." When you go through an office area, where people are using "enterprise" software all day, make a mental note of the little pieces of paper taped to their monitors and cube walls, with written-out instructions for getting through everyday tasks. One thing is that they don't want to be forced to re-make those instructions, which may have been discovered at great cost.
- b112 3y ago
  Yep. Some industries, at this point in time, should be using the same compute and toolkit in 100+ years. My mechanic is using software he bought in the 90s, in an emulator, becuae why change? What's the point? He enters customer names, he books appointments, he inputs inventory, he bills. Nothing has changed in 30 years, norhing will change in another 30. It's barely a gui by today's standard, and works wonderfully. Why transition to another POS system? Why worry about conversion of current data? And the stuff he has is rock solid. All the new stuff he tried has bugs, and the bug fixed versions have different bugs. You wanna be a hard core dev? Develop stuff that will be written to floppies and pressed to CDs, with no internet for updates.
  - nine_k 3y ago
    90s? Look at banks, ticket reservation systems, utility management systems, etc, where COBOL sticks from 1960s, and benefits of a rewrite remain dubious.
- eviks 3y ago
  Another thing is you wouldn't want to impose that great cost of discovering UI for everyday tasks to all the future generations of office area dwellers
ChoHag 3y ago
[dead]

deleted 3y ago

[deleted]

luckman212 3y ago

That's what it should be about. I thought the same thing. I'm so tired of looking for where the "submit" button is or trying to figure out your stupid new password requirements. Must contain: 1 letter, 1 emoji, 2 uppercase, no "Z"s allowed... smfh

eddd-ddde 3y ago
You forgot to include today's wordle answer in your password.

analog31 3y ago

This is why the number-one request from users is: "Please don't change anything." When you go through an office area, where people are using "enterprise" software all day, make a mental note of the little pieces of paper taped to their monitors and cube walls, with written-out instructions for getting through everyday tasks. One thing is that they don't want to be forced to re-make those instructions, which may have been discovered at great cost.

b112 3y ago
Yep. Some industries, at this point in time, should be using the same compute and toolkit in 100+ years. My mechanic is using software he bought in the 90s, in an emulator, becuae why change? What's the point? He enters customer names, he books appointments, he inputs inventory, he bills. Nothing has changed in 30 years, norhing will change in another 30. It's barely a gui by today's standard, and works wonderfully. Why transition to another POS system? Why worry about conversion of current data? And the stuff he has is rock solid. All the new stuff he tried has bugs, and the bug fixed versions have different bugs. You wanna be a hard core dev? Develop stuff that will be written to floppies and pressed to CDs, with no internet for updates.
- nine_k 3y ago
  90s? Look at banks, ticket reservation systems, utility management systems, etc, where COBOL sticks from 1960s, and benefits of a rewrite remain dubious.
eviks 3y ago
Another thing is you wouldn't want to impose that great cost of discovering UI for everyday tasks to all the future generations of office area dwellers

ChoHag 3y ago

[dead]