As a front-end dev, I disagree. You can make something optimized for utility from multiple perspectives. It might be for power users or for the ability to see as much data in one place, or even to change and configure as many things as possible. But these approaches don’t necessarily make it user friendly. Sometimes the most usable flow requires deoptimization.
Have you seen the old SAP UIs? Lots of utility. Complicated as hell usability.
As a software engineer, if its utility is high then so is its usability.
As a front-end dev, I disagree. You can make something optimized for utility from multiple perspectives. It might be for power users or for the ability to see as much data in one place, or even to change and configure as many things as possible. But these approaches don’t necessarily make it user friendly. Sometimes the most usable flow requires deoptimization.
Have you seen the old SAP UIs? Lots of utility. Complicated as hell usability.
I guess there’s a reason I run Linux - I can make it work the way /I/ want it to - and not some way somebody at Microsoft thinks I want it to.
As someone who maintains old software and is looking for a new job, you seem to be indicating I should be a back end dev lol
Hard disagree. If your web app needs a user guide, it’s a bad web app. Design has to provide something that’s intuitive to the end user nowadays.
Have you tried reading the man page?
I prefer tldr (or tealdeer)!
Depends on the task. Sometimes you need to aboid sacrificong too much utility.
Just look at the Lemmy UI vs basically every third party app. Same utility but vastly different usability.