Comment by sublinear
20 hours ago
Fallback states are generally a ton of work that don't benefit the direction that the PM or broader business would want to go anyway.
It's a pet peeve of mine that we often say "devs" when we really mean "the business". It seems to be gamers who started this language. They'll even call the publisher "the devs".
A developer made whatever tech is currently pissing me off. I don't care about the supply chain.
How do you feel about other hot button issues like LLMs, privacy policies, Flock cameras, etc.? By your reasoning, developers "make" those things too.
My point is just to make sure we're pointing the blame at the business where it belongs. It seems very strange how we generally do that, but make exceptions for features. Developers don't control features either. Always blame the business.
This language around "devs" is so twisted and inconsistent that I'm convinced someone is seeding this every time to deflect blame. i.e. "oops just a slip up by the devs" as if features could ever be anything but a massive premeditated effort involving dozens if not hundreds of people planning at least several months ahead of any code being written.
If you want to make a difference, you look at who is running the business. It means what a lot of fanboys cannot admit to themselves. Their favorite companies and CEOs might just be assholes.
I don't want to Godwin this thread so early, but you know what analogy I'm thinking of. If you work as a developer for Google, Microsoft, Flock, CloudFlare, Facebook etc. etc. you are complicit in making the world a crappier place.
Did J. Random Hacker at Google decide to ruin Android app development[1] for everyone? No, but he made it happen. I hate that guy. (Also.)
[1] Edit: I'm referring to this nonsense: https://keepandroidopen.org/
4 replies →