“Common sense” is heavily influenced by cultural norms.
And cultural norms are influenced by scientific studies and government recommendations.
For example, the notion that fat is bad and the main cause of weight gain was not “common sense” before the 1980s.
Some methodologically bad studies and public administration recommendations have made fat look worse than it is.
As a result the public wanted fat replacements -> which led to these “low fat” replacement foods.
Now they contain lots of sugar to keep the taste somehow acceptable.
So now people avoid fat, but load up on sugar.
Funnily at the same time (since the 80s) people get fatter and fatter.
Maybe this common sense to avoid fat but appreciate carbs is what causes people to get fatter?
It has been said that common sense is the collection of prejudices acquired by age eighteen (Einstein) and this does rather characterise it well as the almost exact opposite of Cartesian science. I’m just going back to avoiding all processed food - worked great for me - and walking the dog as often as I can.
Whats the problem of eating horses (forgetting about pets, including drugged horses).
Its tasty, so why not?
Edit: Ah, its metaforic haha
Well i don’t see how people need to eat meat every day anyways.
Its just like needing chocolate every day, its tasty, but really bad.
There’s absolutely, completely, nothing wrong with meat, from a personal perspective. You can eat as much of it as you like. It’s not too great environmentally of course but that’s another matter.
Sigh: Know your math kids. I was peeking around at skip lists to see if I could find a “search finger” version to test out in a given situation I have. No luck, but I glanced at quite of few skip list implementations and what struck me is: people don’t know their math. A classic skip list needs to generate some “levels” with probabilities of : 50%, 25% 12.5%, etc. The ‘fastest’ way this seems to be commonly done (in java-speak) is:
and quite of few do it iteratively. Doh!! This can be cheaply be computed as follows:
Integer.numberOfLeadingZeros(rng.nextInt())
Why? Top bit has a 50% chance of being zero, and likewise for all following bits. So having two zeros in a row is: 0.52 and likewise for n-zeros is 0.5n. End of story. (NOTE: leading zero counts are intrinsic and directly map to a hardware instruction in HotSpot)