I think the website would benefit of listing the lifespan regarding support rather than when it stop selling the device. Right now, it lists the Homepod 1st Gen had a lifespan of 3 years, but mine is still receiving updates regularly.
Most of the problems I faced in the projects I work are caused by developers working only and exclusively with Chrome and not bothering to check their work on Safari and Firefox. The issues that were found with Safari were easy to fix or work around.
Nothing compares to the painful process during ~2005-2010 when it came to support IE6.
I interviewed for them. Questions were Front End related. One of the questions were "how could you find a node in an hmtl by id", to which I answered "using the DOM api, a querySelector would do a good job". The interviewer started hypothesising that the querySelector is not available, so we had to start discussing a whole binary traversal algorithm. If that's not leetcode I don't know what qualifies as it
I ended porting a few clients we had in a company that were already running based on Docker to a Kubernetes cluster. The major issues were trying to push everything there. I think it works very well to manage web clients.
Problems started by trying to push too many things into the clusters. Databases and specially ElasticCache with Kibana to collect metrics from the cluster ended killing the performance.
So it's like everything, some cases are great for K8s, some are terrible. This + a complex abstractions makes it not that developer friendly, but overall it does a good job to run and allow to scale services without having to worry too much with hardware.
I used to work on a company that had MongoDB as the main database. Leaving a lot of criticism aside, the replicaset model for Mongo made the upgrades much easier than the ones in other type of databses.
Funny story about using the alias as suggested, I have a couple of websites I can't unsubscribe because they can't process the character "+" on their forms.