this post was submitted on 06 Apr 2024
787 points (96.3% liked)
Technology
59207 readers
2903 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- 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, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
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
The Microsoft devs have time to do shit like this, but haven't yet gotten the Settings screen as functional as Control Panel was two decades ago...
Do NOT blame the devs for this. They are not the ones to decide the direction of the product or the priority of the tickets they work. Blame upper management for making these poor decisions and the product managers for being spineless and not pushing back.
The devs are the people who, after seeing everything that Microsoft's done for the past 30+ years, decided to take a job there anyway.
That's not a very valid argument.
First and foremost, most devs probably see it as a job and they do what they're told. They don't have the power to refute decisions coming from above.
Second, in this economy where jobs are scarer than a needle in multiple haystacks, people are desperate to get a job.
Third, yes, there may be some Microsoft (M$) fan-people who end up being devs at M$. Sure, they may willingly implement the things upper management may request. However, I'm not sure whether that's true for most of the people who work at M$.
Your comment suggests to shift the blame to the devs who implement the features that upper management request for. Don't shoot the (MSN) messenger.