4 ms·
Better version: There are only two hard things in Computer Science: cache invalidation, naming things, and off-by-one errors.
by Pet_Ant 5y ago
Better version:
There are only two hard things in Computer Science: cache invalidation, naming things, and off-by-one errors.
- jahnu 5y agoThere are only two hard things in Computer Science: cache invalidation, naming things, and off-by-oly two hard things in Computer Scivetëm� dy gjëra të vështira në Shkencën Komp���jute
- jacquesm 5y agoHehe. Ok. That is very funny :)
- gavinray 5y agoI don't get it -- am I slow?
- jacquesm 5y agoBuffer overflow :)
- vaidhy 5y agoThis used to happen in C for me. Basically, you are trying to print a string which has overflowed the allocated length and you get junk printed on the string. C-Strings are null terminated and the system will keep printing till it encounters a null. So, bounds checking and buffer overflows are also hard problems.
- deleted 5y ago[deleted]
- samus 5y agoMemory corruption due to off-by-one errors.
- colejohnson66 5y agoGotta watch out for those nulls :)
- hermitdev 5y agoNow, just toss in a byte order mark, and I think we've a winner!
- MR4D 5y agoBetter better version: There are only two hard things in Computer Science: cache invalidation, and…what did you ask me again?
- kibwen 5y agoThere are only two hard problems in Computer Science: cache invalidation, naming things, off-by-one errors, and remembering to update the documentation.