As other's already pointed out, the author argues about the primary intent of code review. Of course you find bugs while doing it, and that's a nice side effect, but doing code reviews to assert correctness is maybe suboptimal QA. At least that is my take ...
People in traditional cultures are inclined to believe that there is an evil influence involved whenever anything goes wrong. If you're in a culture like that and people believe you can throw curses, you can get material benefit through the threat of throwing curses or make a living throwing curses.
When people were [1] prosecuted for "practicing witchcraft" courts record testimony that promises were made, payments were made, all of that.
Effective curses are not an application of psi (you zapped someone with telepathy) or an evocation of evil spirits, but are loud, noisy, public and supported by the whole social environment, see
I can't say that any magic-user today should practice that sort of stuff, there is the "it gets returned you (3|10) times" bit and that you don't have the social support that the African "witch doctor", Chinese fox medium, Navajo skin-walker, or Italian Nonna who casts the "evil eye". But if you're looking for a social-scientific explanation of how magic works it is a dramatic example.
Just like something that has no direct physical/chemical/biological mechanism to improve your condition can still do so if you believe it will (the placebo effect), it can also worsen your condition if you believe it will - that's the nocebo effect.
Sometimes called non-cebo/none-cebo though I avoid that as starting with “nonce” can be a trigger for the easily befuddled and offended (“Could you be experiencing a noncebo type effect?”, “WHAT DID YOU CALL ME?!”).
As the wikipedia page points out, this is not to be confused with knowcebo, which sounds the same. This is where information leaks break blinding measures and render test results less (or completely not) meaningful.
For example, you could configure your devenv module for the shell you want (which env vars you want set, which packages you want available, etc.), and then re-use this module in other shells.
As such, one of the nice things devenv provides is modules with the compilers/lsp/etc. for different languages, so getting a rust environment is about as simple as `languages.rust.enable = true;`.
I haven't explored using the services/processes aspect of it, but it's got support for things like that to. -- I saw it put somewhere: "oh, like docker-compose, but you can compose the configuration".
