Che_Che_Cole on reddit wrote three years ago this:

simply that we don’t use TDMA anymore, time division multiple access. TDMA was a way for multiple users to share one channel (basically a radio frequency, not unlike a TV channel over the air or tuning your radio to a certain station). It did this by splitting up each user’s signal into short bursts of data. Those bursts/pulses of data are what you heard buzzing in your speaker.

If you’re American you may have noticed back in those days, only Tmobile and ATT did this. They were GSM carriers who used TDMA. Verizon and Sprint used CDMA which was a different technology that did not cause the buzzing speaker because it didn’t transmit in pulses of data.

Newer technologies don’t use TDMA either, so 3G, LTE, now 5G won’t cause a buzz. If you noticed the speaker buzz phenomenon started disappearing in the early 2010s (in the US), that’s why.

https://www.reddit.com/r/explainlikeimfive/comments/slt8j4/comment/hvtdne2/

Some Google folks wrote how they do the Now Playing feature offline with very little resource impact. It’s a great paper to read and quite easy to understand https://arxiv.org/abs/1711.10958

Don’t forget the millennium falcon

I still would have preferred if the top level domain was at the beginning of the URL (com.google). Would have made a lot of pushing way more difficult and more sense.

Shaped to symbolize an engine. The tubing forks are then the pistons.

I say go with Maria or with postgres for all use cases in the beginning. You can even start with sqlite. For most of the use cases you don’t need the scaling and speed of redis, mongodb etc.

If you hit a performance wall with Maria or postgres, you should scale up and optimize before switching to more specialized databases.

If you use an ORM (object relational mapper like Prisma), it should be okay to switch database engines but you don’t want to do that frequently.

My rule of thumb is getting it done first.

Choke Jürgen or cook Jochen. Doesn’t even make sense in German.