this post was submitted on 10 Feb 2026
440 points (97.4% liked)
linuxmemes
29945 readers
377 users here now
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
- Don't get baited into back-and-forth insults. We are not animals.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry will not be tolerated.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudoin Windows. - No porn, no politics, no trolling or ragebaiting.
- Don't come looking for advice, this is not the right community.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
5. ๐ฌ๐ง Language/ัะทัะบ/Sprache
- This is primarily an English-speaking community. ๐ฌ๐ง๐ฆ๐บ๐บ๐ธ
- Comments written in other languages are allowed.
- The substance of a post should be comprehensible for people who only speak English.
- Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
6. (NEW!) Regarding public figures
We all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations. - Keep discussions polite and free of disparagement.
- We are never in possession of all of the facts. Defamatory comments will not be tolerated.
- Discussions that get too heated will be locked and offending comments removed. ย
Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I've only worked once with a UX person and all they did was order other people to produce design documents before any software was written. Like, he didn't design anything himself and didn't even critique others' designs. He made over $300K and eventually left for a job on the west coast making twice as much. He stopped talking to me entirely after the client had me write a prototype TV guide-type app for Blackberry. I created it entirely myself and the client loved it and wanted it released to the public exactly as it was. UX guy insisted (client didn't care at all) that all software needed a design document before any coding could take place, so he was forced to order somebody else to produce a design document for my app which already existed. He wouldn't even look at me when we passed in the hall after this.
I assume that this is not actually what a UX person is supposed to be doing, but I have no idea what their real job is.
The issue with newly emerging and poorly defined professions is that I could apply to any arbitrary position of that title, pretend like I've got expertise in a universal structure for it (managers love structure) and sound vaguely knowledgeable (hiring managers often don't know the subject matter).
By the time they've figured out that I'm not actually contributing anything of value, I'm taking off to other pastures that aren't about to wilt, my experience serving as selling point for the next sucker to hire me.
Of course, the people I just fucked over have no way of telling whether that's me being a fraud or whether it's the entire profession that's actually worthless and overhyped. Some, like you, err on the side of "I assume that person was a cunt", while others default to "UX is completely useless".
I'm guessing that the design documents might've been something in the vein of โuser storiesโ (if I correctly recall their name), which describe what some typical users would want to do with the app, so that the actual UI design would focus on these features being available front and center. This is a very legitimate design technique, and a good designer should always question why any elements must be present in the UI and whether they solve the user's goals.
This Blueman thing would definitely benefit from such approach, because right now it exposes a lot of technical details about which I don't care, while simultaneously making my everyday operations with it inconvenient.
Heh.
Design documents are only useful if those deciding the design are making it and are ready before the coding starts.
And then there is this confusion of which "Design Document" one is talking about. It could be a UI/UX document or it could be the software design document, which would comprise multiple flow-diagrams, helping anyone pick up a project for maintenance and extension.
Yeah that dude was just a dick, but probably confidently, and in a field people don't know much about, so he was able to get away with it.
I work with UX people frequently, and while they do love a good style guide, they're usually more concerned with the overall usability, legibility, and accessibility of an application. They're the people who (should) ensure your application works as expected and follows design and accessibility standards.
Ah, this reminded me of another reason this dude hated me. One of my responsibilities with this gig was ensuring that the client's mobile apps passed accessibility testing. Making an app accessible is tedious work and every time we released an update the accessibility would be broken again. I tried to get this dude to bake the accessibility requirements into the design documents themselves on the off chance that the other developers would actually read the documents (lol as if) and make accessibility work from the get-go. He wasn't having it and couldn't be convinced that it mattered if blind people could use the apps or not. I had to sic the client (who faced enormous fines for failed accessibility tests) on him to get him to do it.