The best is when the microwave is still perfectly capable of functioning, but the membrane keypad starts to go bad and then you can't actually use the microwave anymore.
Want to repair just that part because it's the most unreliable and most likely to break? Well LG only sells the entire door as a replacement part and it's $200 despite the fact that the original microwave costs $400.
I think the entire point of this project is show people that they can make a website without having to be afraid of having the type of experience you just described.
If you just use HTML, then the words that you choose to write will be the words that everyone will read.
Any "pixel placement" is optional and shouldn't be a detering factor.
I think there's a universe where there is no overlap between engineers/PMs who work on the actual DB product and website/content marketing site.
The marketing space is filled with all kinds of "plug and play" SaaS providers which offer detailed customer journey data and sometimes it's just straight up easier to add an "accept all" consent banner than to try and allow for hot loading specific 3rd party libraries based on customized consent options.
Is it the right thing to do? In my opinion, no. But I can also understand a situation where decisions were made on marketing tech before understanding the technical privacy implications. And then the implementation is handled by a team (potentially much smaller) that does not work on the actual product.
Want to repair just that part because it's the most unreliable and most likely to break? Well LG only sells the entire door as a replacement part and it's $200 despite the fact that the original microwave costs $400.