4 ms·
I thought the two hardest problems were: 1) naming 2) cache invalidation ... 3) off-by-one errors
by xarope 6y ago
I thought the two hardest problems were:
1) naming
2) cache invalidation
...
3) off-by-one errors
- waheoo 6y agoI feel like we should have solved the naming problem as an industry by now. Alas.
- layer8 6y agoIt’s actually the hardest one of the three, being outside the grasp of formal methods.
- kreeben 6y agoTo solve this problem we would need to first understand the human mind, how it stores data, how it does computation, and how it interacts with names. So we would need the same set of information that we would need for creating AGI. A solution is probably only a couple of months/decades away.
- waheoo 6y agoI really have to disagree, why can't you devise a formal method? - a good name should be descriptive - avoid being overly clever, call a spade a spade - don't optimise for generalisation, naming things is a time to be specific - aim for short but not at the expense of losing context - avoid redundancy in naming of things nearby, leverage spatial context - avoid qualifiers or type information where possible - type should be obvious from context and use, if it's not qualify or refactor Anything else?
- layer8 6y agoThose aren’t formal definitions. “Formal” means, at the very least, that the specification is done in a formal language, and usually that conformance to the specification can be checked mechanically, that is, by a computer. https://en.m.wikipedia.org/wiki/Formal_methods https://en.m.wikipedia.org/wiki/Formal_methods
- Ancapistani 6y agoI'm pretty sure it's: 1) naming 4) concurr2) cache invalidationency ... 3) off-by-one errors
- hesdeadjim 6y agoLove this.
- deleted 6y ago[deleted]
- edgyquant 6y agoYou forgot 0) Race consegmentation fault (core dumped) (I know I was ninja’d but didn’t see until after)
- account42 6y agoFWIW, your version has the nice touch of also introducing a 0th item.