5 ms·
Wait a minute, I always thought the two hard things were cache invalidation, naming things and off by one errors.
by chrisweekly 12y ago
Wait a minute, I always thought the two hard things were cache invalidation, naming things
and off by one errors.
- kachnuv_ocasek 12y agoNo, those are the four hard things.
- user24 12y agocondition. I'm pretty sure the fifth is a race
- scarecrowbob 12y agoNaw, it's probably graceful expansion. Or maybe that is 6th?
- mbreese 12y agoIn the "expanded" set, there are technically three hard things - you forgot dealing with February 29th.
- IgorPartola 12y agoDaylight savings time... I mean unless you do things like a human, that is in UTC. Otherwise, be prepared for having at least one hour a year when your software does not work.
- drivingmenuts 12y agoI got burned in a tech interview with off-by-one errors. I had signed into a shared editor to do some simple practice stuff for the interviewer. He noted the off-by-one errors as a concern. I was thinking: this is untested, unreviewed, 2-minute code that shows I can at least do some sort of problem solving. I'm nervous, don't know you, kinda worried about the tone of this interview and you're worried about off-by-one errors. Kinda glad I didn't get that one. Wish I'd just hung up on the guy.
- wpietri 12y agoI feel for both you and him. The problem with getting praised a lot for being smart is that you then feel obliged to say smart-sounding things often, and being critical is an easy way to sound smart. It's even worse if you're hired to be smart. So the guy, if he wasn't a total tool, was probably thinking: I wish I could just be coding, but instead I'm supposed to interview a bunch of people in a way that guarantees it will be awkward. And shit, I just got nervous and said something that sounds insulting. I wish I could just hang up.