Hey, I want your opinion on code reviews, what is the best way to use them in a professional environment? Pick one of the following and give me your thoughts (from the most forgiving to the most strict):

1. no code reviews, they are useless
2. optional code reviews
3. mandatory reviews on code that is already merged, optional fixes
4. mandatory reviews on code before merging (like a pull request), with a time-frame for optional fixes (i.e. whether to fix what has been pointed out is up to the author), merge will occur anyway.
5. mandatory reviews on code before merging (PR) with mandatory fixes.

Of course in open source development with public contributions, you'll often see (5), but I'm not convinced it could work in professional dev.

Edit: I'm talking about a team of 5 mid to senior devs (no junior or interns) working on a 2-3 year project without many security concerns, but feel free to give me your general opinion.

Apparently Europe finally got Whatsapp to enable 3rd party chats making it easier to switch to more privacy friendly alternatives article However the only other app that currently works with it is "BirdyChat"??

Have anybody found any news about when serious alternatives will be integrated?

Bought a new PC, and I was measuring its consumption out of curiosity. I noticed something weird (to me): when the PC is off (in fact, I completely disconnected the PSU and did the same test), there is quite some current running in the power cable to the PSU (0.15A).

Further measures showed a power factor of (almost) zero, and I can actually measure a capacity of 2uF across the PSU ac input.

I did the same thing on an older PC I have, and there is no current / capacity. So what would the reason of a capacitor across the mains on the input be in a PSU?

PS: the PSU is a Thermaltake Toughpower GF A3 1050W

Edit: I found some official measurements for this specific PSU: https://www.cybenetics.com/evaluations/psus/2249/ that have 40W standby apparent-power by design