(I can't find the artist's webpage to link to, just some credits saying that this might be a translated Russian comic posted by Piterskii Punk)
this post was submitted on 15 Sep 2024
1083 points (98.7% liked)
Comic Strips
12577 readers
3138 users here now
Comic Strips is a community for those who love comic stories.
The rules are simple:
- The post can be a single image, an image gallery, or a link to a specific comic hosted on another site (the author's website, for instance).
- The comic must be a complete story.
- If it is an external link, it must be to a specific story, not to the root of the site.
- You may post comics from others or your own.
- If you are posting a comic of your own, a maximum of one per week is allowed (I know, your comics are great, but this rule helps avoid spam).
- The comic can be in any language, but if it's not in English, OP must include an English translation in the post's 'body' field (note: you don't need to select a specific language when posting a comic).
- Politeness.
- Adult content is not allowed. This community aims to be fun for people of all ages.
Web of links
- !linuxmemes@lemmy.world: "I use Arch btw"
- !memes@lemmy.world: memes (you don't say!)
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I was gonna say, clients aren't the only ones.
Feels like a lot of developers and especially UX designers have a bad habit of disappearing up their own asshole nowadays.
It's a reason why sometimes an open source project manages to be way better than a comparatively well resourced commercial offering. When the developers are the users, they will get the nuance of things.
Works well for a lot of "power user" software where the users are either developers, or at least similar mindset as a developer. Sometimes open source doesn't deal too well with making things simple without power user features that casual users may find confusing or distracting.
In my experience developing In-House custom software it's more "Managers" and "End-users": basically the requirements for the software that's developed are defined by the manager overseeing an area and hence based on their point of view of the business process they oversee, which is often not at all the same point of view as the people working in that process.
I've seen again and again software being made exactly to the spec provided by team/area management and then turning out to have lots of problems for the actual users to use.
In my experience the best results come from having the developers talk directly with the end-users, even if the language the devs tend to speak and their preconceptions at first don't match those of the end-users.