this post was submitted on 13 Nov 2025
680 points (98.6% liked)
Technology
76808 readers
3045 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
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
That's one thing I love about FOSS, that the only stakeholders are the devs and the users. The goal is to make software that's good at what it does.
When it comes to any tech company's product, you not only have all the stakeholders that corrupt the end product, but you have giant teams of marketers, designers, engineers, and managers that need to constantly justify their existence and or be efficiently utilized at all times.
Honestly it's like lesser version of enshittification, the tendency of commercial products to always be changing things.
While this is true, designers are constatnly beholden to management (much like programmers are), so while designers would love to create a nice looking usable application, they end up having to go with the mockups that management requested which are of course a worse experience for the end-user.
It's really sad.
i feel like a lot of useless bullshit wouldn't be made if managers and execs didn't feel the need to validate their useless existence.
In FOSS world, this is only as true for the subset of developers (including both programmers and designers) that are contributing code as their job duties. Additionally that effect is only prominent in projects that are dominated by one organization. Both those things do happen, but there's also numerous exceptions, too.
Some developers are paid to write unrelated proprietary code and the developer also contributes to open source on their free time. Some projects have so many corporate contributors that none of them can single-handedly direct the development.
Oh, sorry, I wasn't referencing the FOSS world with my comment. I was responding to the tech company's part.
My comment was specifically about designers working for companies, with management forcing them to design things in a way that they would rather not.
It's kind of less about designers having to justify their existence (although, yes, there are far more often entire re-designs that seem like nothing else about this) and more about them being forced to create designs that management want, rather than what end-users want.
That's what my comment was about.
I mean, then you're describing bog-standard capitalistic exploitation, and it's not exclusive to designers.
Sure yeah, my comment originally mentioned designers and developers, but I was too tired to remember that in my follow-up comment.
It's hard to be extremely detailed and also remember every single detail of what I was mentioning as well.
Oh I'm well aware, that's why I threw in the part about needing to be utilized. Because even if the engineers are good with their finished product, some VP will eventually ask their director why the team's output has dropped or why they have so many people for so little work.
I'm an engineer working on a new product right now. Fortunately we're a small outfit with niche customers.