I think it’s probably because we’ve shifted away from shipping software as a product, and onto software as a service. I.E. in the 90s if win 95 irreversibly corrupted, that would be devastating to sales.
But today with windows 11? Just roll it out in one of the twenty three testing branches you have and see what happens, and if shit does break. Just work around it. It’ll be fine. Even if something does happen, you can most of the time, fix it and roll out a new update.
And i also think it’s moved to be more team centric, rather than department centric. A lot of the theory is probably more senior team led type responsibility. While everyone writing the code can chip in and add some as well. Developers knowing how to write secure code helps, so they should theoretically also be capable of QA themselves to a degree.
Also there’s a lot more money in shipping shit out the door, than there is in shipping a functional product, unfortunately.
Thank you for your TED talk defining enshitification.
Middle management bloat.
Edit: Bonus points for
Developers knowing how to write secure code helps, so they should theoretically also be capable of QA themselves to a degree.
Which is straight up just saying “why don’t the devs just do it themselves? I’m busy with meetings to whine back and forth with other middle management.”
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !programmerhumor@lemmy.ml
Post funny things about programming here! (Or just rant about your favourite programming language.)
Rules:
Posts must be relevant to programming, programmers, or computer science.
No NSFW content.
Jokes must be in good taste. No hate speech, bigotry, etc.
I think it’s probably because we’ve shifted away from shipping software as a product, and onto software as a service. I.E. in the 90s if win 95 irreversibly corrupted, that would be devastating to sales.
But today with windows 11? Just roll it out in one of the twenty three testing branches you have and see what happens, and if shit does break. Just work around it. It’ll be fine. Even if something does happen, you can most of the time, fix it and roll out a new update.
And i also think it’s moved to be more team centric, rather than department centric. A lot of the theory is probably more senior team led type responsibility. While everyone writing the code can chip in and add some as well. Developers knowing how to write secure code helps, so they should theoretically also be capable of QA themselves to a degree.
Also there’s a lot more money in shipping shit out the door, than there is in shipping a functional product, unfortunately.
Thank you for your TED talk defining enshitification.
Middle management bloat.
Edit: Bonus points for
Which is straight up just saying “why don’t the devs just do it themselves? I’m busy with meetings to whine back and forth with other middle management.”
pretty much yeah lol