Raymond B

If you are looking to contribute to a good, active, and deep-tech OSS project, you will find DiceDB pretty neat. We have opened many interesting, low-hanging good-first issues. These issues are a great starting point to understand how production-grade databases are actually built. The codebase is still in its nascent stage and it is relatively easier to get started with it. So, go for it :) github.com/dicedb/dice by the way, DiceDB is the world's first truly real-time database with SQL-based reactivity. We are breaking down Redis and architecturally changing it to become optimized for modern hardware - making it multi-threaded - added SQL support - native JSON support, and so on If you cannot contribute patches, you can help with the reach by leaving a star on the repo and sharing this post :)

I saw many engineers blaming the outage on Microsoft 🤦‍♂️ SWEs blaming without knowing the root cause is concerning. It is not Microsoft, it is Crowdstrike who released an update for Windows that had a bug. The patch runs in Kernel mode to monitor system activity at a low level. Because it was running in Kernel mode, the buggy code was trying to access an invalid memory location that triggered a panic and which showed Blue Screen of Death. The name of the driver file that had the buggy update is "C-00000291.sys", deleting it fixes the issue and unfortunately this needs to be done manually. Microsoft has nothing to do with it.