Software devs also hate UX/UI Designers.
And Product Owners.
And Scrum Masters.
And Software Architects.
And Security/Compliance Managers.
And QA Testers.
And worst of all… Software devs.
I would never be able to explain coherently the difference between UX and UI people. I’ve only worked for one company that even had a UX guy on staff. He was paid an insane amount of money (close to half a mil per year) and as far as I could tell did absolutely nothing except insist that certain procedures be followed rigorously. He never designed anything at all himself.
He was the only coworker I’ve ever had who ended up refusing to speak to me or even acknowledging my existence. This came about because I wrote a TV Guide-type app for Blackberry which our client loved and insisted on having added to their corporate app. The UX guy insisted that no app could be produced unless it was preceded by a formal design document, so he was forced into the situation of having to produce a design document for an app that had already been written, which completely broke his brain. Or rather, he was forced into ordering someone else to do this, since as I mentioned he never actually did anything himself.
He eventually left because he got a job offer for way more money lol. I guess I shouldn’t make fun of somebody who had the system figured out far better than me.
I thiiiink the thing with UX is that they consider overall usability and click paths, while UI is more down in the reeds and looks at more specific things like alignment, design language and color choices. The line between seems pretty blurry though, and how it works in practice probably differs widely between companies.
A good UX/UI team can make or break a project. As a Frontend-focused software dev, that kinda hurts admitting. It’s just always very frustrating to deal with them, because designers are specialized in design. So they neither know about technical limitations that make trivial seeming things hard (like conditionally changing a buttons color based on server state) but they also don’t know about technical “freebies” that the libraries we use give us (like just telling a component that they can overflow and render things wherever you want in ways that Figma would never allow you to design). So talking to them is hard, which leads to a spiral of never talking to them, fucking up the UX, and then dodging them while they try to get the UX fixed. That just sucks for everyone involved.
Hating the Design Team is apparently such a universal experience that Josh W Comeau has a great article on it. Really worth the 15min read, if you want to improve your relationship with the design team!
like just telling a component that they can overflow and render things wherever you want in ways that Figma would never allow you to design
This is probably the one reason I hate designers the most. My personal biggest gripe about mobile apps (and desktop apps for that matter) is when there is plenty of screen space available to show a long piece of text (like the name of a song or movie, for example) but the allocated display area is small and the text is just truncated with ellipses. I had the experience more than once of being handed a design like this and simply modifying it to flow and allow full display of the text although this made the height of the element variable (usually not even requiring any special code or library, just HTML which handles this automatically). The designers always objected to this modification and insisted that it be removed, and the managers always backed them up on the grounds that my modification would take too long to implement - even though it had already been implemented (trivially) and would take even more time to remove.
That is to say, the designers always objected when I was foolish enough to mention that I’d done it. I did eventually learn that lesson.
I would never be able to explain coherently the difference between UX and UI people.
In theory, UX deals with the psychology behind it: What do people want that our product can provide? Does our product communicate that it can do so? Do people understand how to use the product? Does the product guide them through usage helpfully? Are they satisfied with the result?
Perhaps most nebulously: How do they feel before, while and after using the product, independent of the product itself, and how does that impact their experience? For instance, if you’re buying a train ticket, you might already be stressed and annoyed, so you’ll have less patience.
Source: My wife, who had UX as the focus of her undergrad.
In practice, a lot of people are like you in that they don’t really know or grasp the field, particularly managers who aren’t qualified to make the hiring decisions they do and accordingly there’s always gonna be people capitalising on that ambiguity and grifting their way to a cushy “I’m important and get to have a say, so pay me well” job.
Some of us are real go-getters and realize we can bring the farm to us long before we retire! I am currently typing this on my Linux couch computer wearing lightweight clothes with literal dirt smeared on them, on a dinner break before I return to the back yard and continue today’s construction project. Sometimes being a “farmer” also means becoming a carpenter!
Granted, it works much better for the suburban homeowner than anybody living in a city and/or an apartment.
And when I refer to myself as a “farmer,” all my animals are family pets cared for as a hobby. There is 0% business plan. Well, probably negative %. When we have too many animals (usually too many fish in the pond) we give them away for free!
That does sound nice, but in writing this from my work from home location right near to the beach. But my second choice would be someplace with a lot of woods and some good star gazing.
Software devs hate users
Software devs also hate UX/UI Designers.
And Product Owners.
And Scrum Masters.
And Software Architects.
And Security/Compliance Managers.
And QA Testers.
And worst of all… Software devs.
deleted by creator
Damned software devs, they ruined software!
Software devs sure are a contentious bunch
You’ve just made an enemy for life!
I would never be able to explain coherently the difference between UX and UI people. I’ve only worked for one company that even had a UX guy on staff. He was paid an insane amount of money (close to half a mil per year) and as far as I could tell did absolutely nothing except insist that certain procedures be followed rigorously. He never designed anything at all himself.
He was the only coworker I’ve ever had who ended up refusing to speak to me or even acknowledging my existence. This came about because I wrote a TV Guide-type app for Blackberry which our client loved and insisted on having added to their corporate app. The UX guy insisted that no app could be produced unless it was preceded by a formal design document, so he was forced into the situation of having to produce a design document for an app that had already been written, which completely broke his brain. Or rather, he was forced into ordering someone else to do this, since as I mentioned he never actually did anything himself.
He eventually left because he got a job offer for way more money lol. I guess I shouldn’t make fun of somebody who had the system figured out far better than me.
I thiiiink the thing with UX is that they consider overall usability and click paths, while UI is more down in the reeds and looks at more specific things like alignment, design language and color choices. The line between seems pretty blurry though, and how it works in practice probably differs widely between companies.
A good UX/UI team can make or break a project. As a Frontend-focused software dev, that kinda hurts admitting. It’s just always very frustrating to deal with them, because designers are specialized in design. So they neither know about technical limitations that make trivial seeming things hard (like conditionally changing a buttons color based on server state) but they also don’t know about technical “freebies” that the libraries we use give us (like just telling a component that they can overflow and render things wherever you want in ways that Figma would never allow you to design). So talking to them is hard, which leads to a spiral of never talking to them, fucking up the UX, and then dodging them while they try to get the UX fixed. That just sucks for everyone involved.
Hating the Design Team is apparently such a universal experience that Josh W Comeau has a great article on it. Really worth the 15min read, if you want to improve your relationship with the design team!
This is probably the one reason I hate designers the most. My personal biggest gripe about mobile apps (and desktop apps for that matter) is when there is plenty of screen space available to show a long piece of text (like the name of a song or movie, for example) but the allocated display area is small and the text is just truncated with ellipses. I had the experience more than once of being handed a design like this and simply modifying it to flow and allow full display of the text although this made the height of the element variable (usually not even requiring any special code or library, just HTML which handles this automatically). The designers always objected to this modification and insisted that it be removed, and the managers always backed them up on the grounds that my modification would take too long to implement - even though it had already been implemented (trivially) and would take even more time to remove.
That is to say, the designers always objected when I was foolish enough to mention that I’d done it. I did eventually learn that lesson.
In theory, UX deals with the psychology behind it: What do people want that our product can provide? Does our product communicate that it can do so? Do people understand how to use the product? Does the product guide them through usage helpfully? Are they satisfied with the result?
Perhaps most nebulously: How do they feel before, while and after using the product, independent of the product itself, and how does that impact their experience? For instance, if you’re buying a train ticket, you might already be stressed and annoyed, so you’ll have less patience.
Source: My wife, who had UX as the focus of her undergrad.
In practice, a lot of people are like you in that they don’t really know or grasp the field, particularly managers who aren’t qualified to make the hiring decisions they do and accordingly there’s always gonna be people capitalising on that ambiguity and grifting their way to a cushy “I’m important and get to have a say, so pay me well” job.
Sysadmins hate computers.
Sysadmins hate node_modules/
And themselves from a month ago…
… when they said to themselves "This little piece of code is fine, I don’t need to change it now. I’ll just refactor it later. "
And technology. That’s why they all fantasize about living on farms
Some of us are real go-getters and realize we can bring the farm to us long before we retire! I am currently typing this on my Linux couch computer wearing lightweight clothes with literal dirt smeared on them, on a dinner break before I return to the back yard and continue today’s construction project. Sometimes being a “farmer” also means becoming a carpenter!
Granted, it works much better for the suburban homeowner than anybody living in a city and/or an apartment.
And when I refer to myself as a “farmer,” all my animals are family pets cared for as a hobby. There is 0% business plan. Well, probably negative %. When we have too many animals (usually too many fish in the pond) we give them away for free!
That does sound nice, but in writing this from my work from home location right near to the beach. But my second choice would be someplace with a lot of woods and some good star gazing.