906 karma · joined June 19, 2018
Books like Influence the art of persuasion and Thinking fast and slow wrestle a bit with the morality of studying this kind of stuff.
It’s certainly possible to misuse the insights to manipulate others, but it’s also important to be able to recognize when and how you’re being manipulated.
A hash table is a remarkable data structure that can be used to implement many algorithms simply and efficiently.
This efficiency depends on being able to create small (say 32- or 64-bit) and nearly-unique “hashes” for your data. For example, to hash user names, it wouldn’t work very well to just use the ASCII code for the first letter of the names, because then a lot of usernames would map to the same number. That’s called a collision. If there are a lot of collisions, hash tables become very inefficient.
A better approach would be to grab bits from the entire username, and smash them together somehow so that “throwaway_1237” and “throwaway_12373” still username different numbers.
Hash functions do this mapping. The property of “avalanche” describes how good of a job they do at avoiding collisions.
There’s generally a tradeoff between (1) how fast the actual hash function is, and (2) how good of a job it does of avoiding collisions.
World-class hash functions look remarkably weird, multiplying and xoring and shifting by strange amounts. It’s very hard for humans to look at these cryptic functions and guess how well they will do.
So this code is trying out a bunch of hash functions at random and baking them off against each other. This is cool because success here could improve real-world performance of a core data structure used across many languages and libraries.
I didn’t know about this publication at all. Wikipedia doesn’t even have a page about it.
This other site describes it as qanon nuttery.
I’m sure the folks who worked on this are hard working and dedicated and all of that, but the entire IEEE standards process seems like a backward, political, and entirely pay to play model.
Based on my experience, they won’t even talk to you unless your company joins their consortiums and whatnot. And why would they? Their members benefit directly from the “moat” of complexity they have created. As an outsider, you may as well not even bother trying to report errors, etc.
“Liskov substitution principle” for instance is something I had to look up. I can read it and say, “oh, duh, yes that’s a key part of what interfaces are even for.” I’ve built with it for decades now.
The term SOLID was apparently introduced in 2004. It would be a shame to reject good programmers who can opine intelligently on these principles, but who have not internalized this particular jargon.
You might be overly hard on yourself here. Everything is a spectrum. My usual failure mode seems to be excessive patience when folks aren’t delivering. It is extremely bad when you let it fester. Lots of stuff doesn’t matter, but when important things aren’t happening, you really need to jump on it fast and insist on the high bar.
What moral justification is there for them to hoard absurd sums of money, particularly when we have folks without homes and kids in poverty?
More optimistically, at least it’s possible to diagnose these mistakes and work to mitigate them. The fact that we could now start treating auto collisions as seriously as plane incidents might be reason to hope.