It frustrates me because it seems like the opposite of mindful engineering. I feel like that's the "we don't give a shit about resources" development mantra fo

It frustrates me because it seems like the opposite of mindful engineering. I feel like that's the "we don't give a shit about resources" development mantra for you, banking on the ever increasing hardware limits that everyone will purchase in never-ending ~2 year cycles. "Ah, it's a nice morning with so many free gigabytes of RAM, calm CPU cycles and sunshine. Let's slap a few questionable libraries and a bunch of chatty analytics modules into the build." It doesn't help that a lot of major businesses work with contractors and consultants in relatively short-term gigs where feature development is king even if your application is reasonably feature complete. It's hard to improve a complex application if your domain knowledge and technical knowledge isn't quite there due to short time spent at the company (and likely no real personal invest in the product). Also, in mid to large sized companies, constant unwarranted changes to please a fat layer of middle management which needs to pretend to have some sort of impact may lead to crappy development. Let's just change the UI and UX for the sake of it with 5 additional libraries, 2 more processes so that manager XYZ has something to show for his PowerPoint presentation. Don't you dare work on technical debt and refactoring, we need new features to make management happy! Excluding possible external dependencies that might have broken or standards that might have changed, what did Netflix REALLY add to their app from a user perspective since it ran perfectly well on the iPad mini 2 in 2014?