I really dislike this sentiment in this context. This sentiment is about applications made for people who barely use computers. It’s for like… iPhone apps to order food. This sentiment is just incorrect when it comes to technical tools made for professionals.
Apply this to like any other profession and it makes it obvious how nonsense it is.
If you need a manual to disassemble this engine, it’s a terrible engine.
If you need a manual to pilot this helicopter, it’s a terrible helicopter.
If you need a manual to operate this electron microscope, it’s a terrible electron microscope.
This is a very apples to 40kg bag of quick set concrete conparison.
If your team od professionals need to spend all the time learning how to do basic shit from manuals, you just wasted hundreds of thousands in wages. And you are going to waste more monwy every time you hire someone new.
Engines all function basically same and once you know how to assemble or dissassemble one, you use the manual as reference. And unless the engine is shit you really never need to take it apart.
Aircraft are regularly being praised for being easy to fly as it is a very desirable quality. Usa designed ww2 tanks to be easy and intuitive to drive for service men since it sped up training, reduced costs, reduced the amount of accidents etc.
There are entire degrees and careers dedicated to better user experiences and good designs cause bad design is just fucking stupid and expensive. You pay proffessionals for their brains. Do you want to waste your money ohln their brains being used to run through the manual every day and remembering in ehich stupid ass menu or hotkey the needed action is, or for them to solve the problems they came here to solve?
Id like to hear a single reason why shit ass ux and obtuse learning experience is good, acually, since you have not posted any.
I see where you’re coming from, but I’ve encountered many things in professional applications where the UX baffles me. I know what I’m trying to get the program to do but it seems to require me to keep notes as to how to achieve the thing. Menu entries with needlessly cryptic names, heavily nested functionality, that sort of thing.
While I believe everything I’ve said I also believe that 90% of graphical applications are dogshit and 99% of closed source software is dogshit and I don’t think these things can change due to conflict of interest. I very strictly use only open source software in my workflow and because of this, when I have a problem with the tools I just fix them myself.
Even if I had that luxury, I really don’t want to spend my time fixing someone else’s UI. I have my own projects to work on.
I used to do a lot of user testing and I think it’s something every bit of software needs. I really admire projects that decide to do big pushes on usability and papercuts.
I don’t know, am I? I tried to keep it civil, until you argued - multiple times - that everyone who thinks that your software of choice is cumbersome is just too dumb to learn it and got downvoted almost every time. Then you gave me a snippy reply when I politely asked what your professional relationship with that software is.
By the way: software engineer, 22 years hobby, 16 years professional.
Maybe we should just accept that everyone has different needs and experiences and not judge others for not liking the things we like? Does that sound fair?
I really dislike this sentiment in this context. This sentiment is about applications made for people who barely use computers. It’s for like… iPhone apps to order food. This sentiment is just incorrect when it comes to technical tools made for professionals.
Apply this to like any other profession and it makes it obvious how nonsense it is.
This is a very apples to 40kg bag of quick set concrete conparison.
If your team od professionals need to spend all the time learning how to do basic shit from manuals, you just wasted hundreds of thousands in wages. And you are going to waste more monwy every time you hire someone new.
Engines all function basically same and once you know how to assemble or dissassemble one, you use the manual as reference. And unless the engine is shit you really never need to take it apart.
Aircraft are regularly being praised for being easy to fly as it is a very desirable quality. Usa designed ww2 tanks to be easy and intuitive to drive for service men since it sped up training, reduced costs, reduced the amount of accidents etc.
There are entire degrees and careers dedicated to better user experiences and good designs cause bad design is just fucking stupid and expensive. You pay proffessionals for their brains. Do you want to waste your money ohln their brains being used to run through the manual every day and remembering in ehich stupid ass menu or hotkey the needed action is, or for them to solve the problems they came here to solve?
Id like to hear a single reason why shit ass ux and obtuse learning experience is good, acually, since you have not posted any.
I see where you’re coming from, but I’ve encountered many things in professional applications where the UX baffles me. I know what I’m trying to get the program to do but it seems to require me to keep notes as to how to achieve the thing. Menu entries with needlessly cryptic names, heavily nested functionality, that sort of thing.
While I believe everything I’ve said I also believe that 90% of graphical applications are dogshit and 99% of closed source software is dogshit and I don’t think these things can change due to conflict of interest. I very strictly use only open source software in my workflow and because of this, when I have a problem with the tools I just fix them myself.
Even if I had that luxury, I really don’t want to spend my time fixing someone else’s UI. I have my own projects to work on.
I used to do a lot of user testing and I think it’s something every bit of software needs. I really admire projects that decide to do big pushes on usability and papercuts.
May I ask what you do professionally?
Take a wild guess
Unemployed, never had to use a piece of software to make money.
computer programming 17 years hobby 5 years professional
you are really in a mood today
I don’t know, am I? I tried to keep it civil, until you argued - multiple times - that everyone who thinks that your software of choice is cumbersome is just too dumb to learn it and got downvoted almost every time. Then you gave me a snippy reply when I politely asked what your professional relationship with that software is.
By the way: software engineer, 22 years hobby, 16 years professional.
Maybe we should just accept that everyone has different needs and experiences and not judge others for not liking the things we like? Does that sound fair?
listen man. you think i’m trolling you, i think you’re trolling me, we can just not talk.
No wonder you don’t know what good ux is.