> I believe, we are beyond the point of “bad software written, bad software deployed, business as usual” point long ago when AWS/GCP/Azure became an important requirement in job description.
> A bad piece of software can be decently hidden by burning more money in cloud bills, which gives the inflated sense to the leadership that their products are doing global scale ground breaking.
Doesn't this apply to almost all software out there nowadays?
Bloated enterprise frameworks (lots of reflection and dynamic class loading on the back end, wasteful memory usage; large bundles and very complicated SPA on the front end), sub optimal DB querying, bad architectures, inefficient desktop and mobile apps built on web technologies because of faster iteration speed, things like messing up OS package management where it's not easy to halt updates and they don't integrate well with the rest of the system (e.g. snap packages), messy situation with operating systems where you get things like ads in the start menu or multiple conflicting UI styles within it (Windows), game engines that are hard to use well to the point where people scoff just hearing UE5 and so on.
Essentially just Wirth's law, taken to the maximum of companies and individuals optimizing for shipping quickly and things that catch attention, instead of having good engineering underneath it all: https://en.wikipedia.org/wiki/Wirth%27s_law
Not the end of the world, but definitely a lot of churn and I don't see things improving anytime soon. If anything, I fear that our craft will be cheapened a lot due to prevalence of LLMs and possible over-saturation of the field. I do use them as any other tool when it makes sense to do so... but so does everyone else.