11–20 of 349 posts
I certainly agree. The one case where this isn't necessarily true is a fresh boot. Granted, my reference point starts from the 90s, and that's assuming you're booting from an HDD (not an SSD, flash, or restoring cached state from quick/fast boot).
This! I once took over programming a point of sale system that our (internal to the company) users were complaining about. Turns out there was no concept of tab sequence, you had to use the mouse for everything. I asked the previous programmer to show me how to use the form he created, and he started typing a phone number using the top row of the keyboard instead of the numpad. But hey, it had lots of javascript!
Was originally a tweet-storm -> https://twitter.com/gravislizard/status/927593460642615296 , if anyone is confused by the stream-of-consciousness style. It is frustrating that I've got a machine on my desk more powerful than supercomputers a generation ago, and it locks up and can't refresh the screen as fast as my relatively slow typing on a regular basis...
I don't mean to detract from the point, but this piece would be helped so much by properly fleshing it out into an article. presenting it as a sequence of 92 tweets is combining the worst of both worlds.
This! I once took over programming a point of sale system that our (internal to the company) users were complaining about. Turns out there was no concept of tab sequence, you had to use the mouse for everything. I asked the previous programmer to show me how to use the form he created, and he started typing a phone number using the top row of the keyboard instead of the numpad. But hey, it had lots of javascript!
For example, it was a common piece of advice that if clicking a button opens up a dialog box, there should be a brief animation showing the box expanding from the direction of the button, so the user would associate the clicking of the button with the appearance of the box and understand where it came from. This does actually improve usability the first few times it happens, but over hundreds of iterations these tiny delays really slow down the overall experience of using the interface.
It's fascinating how we tend to over-engineer and bloat things.
This! I once took over programming a point of sale system that our (internal to the company) users were complaining about. Turns out there was no concept of tab sequence, you had to use the mouse for everything. I asked the previous programmer to show me how to use the form he created, and he started typing a phone number using the top row of the keyboard instead of the numpad. But hey, it had lots of javascript!
For those of us that have been fortunate enough to avoid having a job that involved an adding machine or cash register the number pad is an awkward AF to use. Conversely the top keyboard row is in range for touch typing.
I wonder how much of this is a result of UI designers deliberately putting tiny delays/animations into their UIs to make them more "usable"? For example, it was a common piece of advice that if clicking a button opens up a dialog box, there should be a brief animation showing the box expanding from the direction of the button, so the user would associate the clicking of the button with the appearance of the box and u…