4 ms·
> Also just for fun, here's a creative stab at my own explanation. I know you said "just for fun", but I really think we need to do better than these types of
by Wowfunhappy 8y ago
> Also just for fun, here's a creative stab at my own explanation.
I know you said "just for fun", but I really think we need to do better than these types of explanations.
I remember many years ago, I was wondering what the heck hyper-threading was, and I came across a video that compared it to a bowl of cereal. Even though you only have one mouth, you'll be able to eat the cereal more quickly if you use both your hands, instead of just one.
I watched this video, and felt gratified, and closed the browser window... and then suddenly realized that I still had no idea what hyper-threading was, only that I should use both my hands if I'm ever in a cereal-eating competition.
A better explanation would have gone something like, "CPUs solve math problems more quickly than we can give them problems to solve. Hyper-threading queues up additional sets of problems that the CPU can switch to when it would otherwise be doing nothing."
Analogies are useful tools, but usually only after we have some understanding of the real version.
- Fnoord 8y agoAnalogies are great to memorize the content. They don't explain the content because they're not 1:1 translatable.
- afiori 8y agoDoes that mean that analogies themselves are an analogy of hash functions? (not serious; hope it is not against the guidelines) More seriously analogies are better for a bigger picture of a complex system, as they effectively describe mode of interactions. The dog/smell analogy was not bad but you have to also add a role for the other actor in the system (here I would say: the third party, and the database)