5 ms·
I thought the two hardest things in CS was naming things, off-by-by one errors, and cache invalidation, but I must be remembering that incorrectly.
by biomcgary 3y ago
I thought the two hardest things in CS was naming things, off-by-by one errors, and cache invalidation, but I must be remembering that incorrectly.
- klabb3 3y agosynchronization. Don’t forget
- sdenton4 3y agoThe whole reason for the off by one error in the standard joke is that we forgot to use a mutex.
- actionfromafar 3y agoDon’t forget synchronisation.
- spenczar5 3y agosynchronization, too
- Sduic 3y agoOK, the two hardest things in CS are naming things, off-by-one errors, cache invalidation, and synchronisation...and consensus... I'll come in again.
- hnburnsy 3y agoDamn you beat me to it, I knew this felt like a Monty Python skit... >“Nobody expects the Spanish Inquisition! Our chief weapon is surprise... surprise and fear... fear and surprise... Our two weapons are fear and surprise... and ruthless efficiency.... Our three weapons are fear, and surprise, and ruthless efficiency... and an almost fanatical devotion to the Pope... Our four... no... Amongst our weapons... Amongst our weaponry... are such elements as fear, surprise... I'll come in again.”
- bostik 3y agoConsensus is a distributed systems problem. And in that space there are only two hard problems: 2. Exactly-once delivery 1. Guaranteed order of messages 2. Exactly-once delivery