But anyways much of what you are listing is just more stuff that sounds complex or is not needed. It exist because there was money and it was a big bloated organization. It’s not needed to run the core business and frankly the cost of those things are still small. The number of users don’t change their engineering cost, or at least should not.
The promise of software is exactly the return on investment is not affected by the number of people who use it.
Also. You got me at dynamic content, that is the job of the software, not a human. If they have yet to provide user friendly interfaces down their editors to manipulate the content on their site without the need to interface with an engineer then they have already failed.
I know this sounds like a rant, and maybe it is. But I am tried of poorly ran companies justifying outrageous team sizes because they simply ignore any good design with their software and how to organize a company to be lean agile and successful.
And how are you deciding what is or is not needed. You're basically saying the company should never innovate or try anything new outside of their existing core business, and should minimize their chances for monetization in new verticals which basically no corporation would ever do. They're always looking for other sources of monetization since thats what investors want.
Everything they do today could be done with under 100 engineers, maybe less.
As bad as the modern web is, if you think embedding media is a hard problem, one of us has clearly gone bat crazy.
(To be clear, I welcome being told why embedding media is a really hard problem, but my experience hosting a self-implemented blog says otherwise.)
I'm not talking about embedding video, I'm talking about custom built JavaScript data visualization elements.