One thing that I would find cool as a follow-up to this article would be something like a decision tree (I understand it would get very complicated, very fast, but it should be fun): I, as a developer, am using AWS/Azure and I need features X,Y,Z, tell me which database I should pick.
Probably even better if it were a model trained extensively on the documentation / features of each individual database and it would also give references to the answer (see how Bing does it).
There's a big difference between wire and syntax compatibility. This compatibility matrix does a nice job of showing the differences between vendors. But yeah, purpose-built databases have a place.
Many decision trees I've seen when NoSQL purpose-built were becoming popular are obsolete now that the main SQL databases have structures, APIs and optimisations for non-relational models: JSONB, Text Search, Timeseries, Documents... Today, the differentiator on architecture goals: converged database vs. multiple services
Not sure why this is news - Amazon is the first company to embrace a hybrid work environment, way before the pandemic... Monday, Tuesday, Wednesday, Thursday, Friday - work from the office. Saturday and Sunday - work from home.
It may be a joke, but this kind of treating employees made it harder and harder for them to justify going through the pain of relocating close to an office with huge property prices around it.
What do you call a person that speaks 2 languages? A bilingual.
What do you call a person that speaks 3 languages? A trilingual.
What do you call a person that speaks 1 language? An American.