You put into words the things I've noticed UIs evolving away from.
It just feels like UIs of software 10,20, even 30 years ago were designed for "operators", people that actually worked with the software for hours at end, and so with a little bit of learning you could be dancing with keybindings and doing stuff as fast as CLI nerds.
Nowadays most seems to be optimized for first hour of use of new user and not much else, and the exceptions are software made "by operators, for operators", like for example KiCAD.
Downside is nowadays in office setting one has to operate 20+ different applications to get work done.
While as operator you would spend more like 80% of your time using the same interface and application.
I could spend my time to type 100WPM but I am not a typist - as a software dev it is quite enough to go with 40-60WPM because it is just small part of my work.
> Downside is nowadays in office setting one has to operate 20+ different applications to get work done.
Like ? Even as a developer I'm not consistently using 20 different "big apps". 2 chat programs, IDE, terminal, mail client, wireshark, maybe some GUI DB tool if I feel lazy that day
> I could spend my time to type 100WPM but I am not a typist - as a software dev it is quite enough to go with 40-60WPM because it is just small part of my work.
Not really about wpm but ability to hit few shortcuts to get where I want instead of navigating thru 4 different panels to get to the one option I need
Indeed you did; half of my brain capacity is currently being used by a background process sifting through everything I remember ever thinking or learning that's associated with computers, to re-evaluate it in context of the difference between "users" and "operators".
Seriously. Until your comment, I thought the two terms to be synonyms.
You put into words the things I've noticed UIs evolving away from.
It just feels like UIs of software 10,20, even 30 years ago were designed for "operators", people that actually worked with the software for hours at end, and so with a little bit of learning you could be dancing with keybindings and doing stuff as fast as CLI nerds.
Nowadays most seems to be optimized for first hour of use of new user and not much else, and the exceptions are software made "by operators, for operators", like for example KiCAD.
Downside is nowadays in office setting one has to operate 20+ different applications to get work done.
While as operator you would spend more like 80% of your time using the same interface and application.
I could spend my time to type 100WPM but I am not a typist - as a software dev it is quite enough to go with 40-60WPM because it is just small part of my work.
> Downside is nowadays in office setting one has to operate 20+ different applications to get work done.
Like ? Even as a developer I'm not consistently using 20 different "big apps". 2 chat programs, IDE, terminal, mail client, wireshark, maybe some GUI DB tool if I feel lazy that day
> I could spend my time to type 100WPM but I am not a typist - as a software dev it is quite enough to go with 40-60WPM because it is just small part of my work.
Not really about wpm but ability to hit few shortcuts to get where I want instead of navigating thru 4 different panels to get to the one option I need
1 reply →
Indeed you did; half of my brain capacity is currently being used by a background process sifting through everything I remember ever thinking or learning that's associated with computers, to re-evaluate it in context of the difference between "users" and "operators".
Seriously. Until your comment, I thought the two terms to be synonyms.