4 ms·

> Or is it literally that cache invalidation is hard? It's literally that cache invalidation is hard. You can also think of "cache invalidation" as a substitut

> Or is it literally that cache invalidation is hard? It's literally that cache invalidation is hard. You can also think of "cache invalidation" as a substitute of concurrent programming: keeping multiple related threads of logic synchronised. >Isn’t cache invalidation on a completely different level as naming things, both conceptually and in difficulty? I'd say it's on a conceptually different level, but not less difficult, and because "naming things" is easy, it's more insidious. From my point of view "naming things" is a substitute for architecting software instead of coding your way out of dead ends whilst inventing a lot of off the cuff names in the process. (of course, in the current climate, such ad-hoc solutions are now the standard, called "design patterns", and people find names that have "Factory" in them twice a normal thing.)

Sesse__ 6y ago
No, naming things is really hard. Well, giving things (functions, variables, classes, algorithms) _bad_ names is easy, giving them good names is hard. For instance, when did you last see a class called <something>Manager? Then consider the fact that “manager” means absolutely nothing.
- uryga 6y ago
  > “manager” means absolutely nothing do you know a better name for "window manager"? i don't mean to hold that up as a paragon of great naming, just genuinely curious what you'd call it. like, i'm no fan of AbstractFactories (or classes for that matter), but i never quite got this sentiment. to me, "manager" suggests that you have a bunch of resources that should be centrally managed (created/freed, whatever), and theres's something (perhaps an object) that handles that. ofc it's really generic, and a more concrete name should be used if possible, but i wouldn't say it's meaningless
- HelloNurse 6y ago
  Both cache invalidation and naming things are hard activities because they require precognition to be done well.
- fegu 6y ago
  Other bad names for variables and database coloumns: type, kind, val.

Sesse__ 6y ago

No, naming things is really hard. Well, giving things (functions, variables, classes, algorithms) _bad_ names is easy, giving them good names is hard. For instance, when did you last see a class called <something>Manager? Then consider the fact that “manager” means absolutely nothing.

uryga 6y ago
> “manager” means absolutely nothing do you know a better name for "window manager"? i don't mean to hold that up as a paragon of great naming, just genuinely curious what you'd call it. like, i'm no fan of AbstractFactories (or classes for that matter), but i never quite got this sentiment. to me, "manager" suggests that you have a bunch of resources that should be centrally managed (created/freed, whatever), and theres's something (perhaps an object) that handles that. ofc it's really generic, and a more concrete name should be used if possible, but i wouldn't say it's meaningless
HelloNurse 6y ago
Both cache invalidation and naming things are hard activities because they require precognition to be done well.
fegu 6y ago
Other bad names for variables and database coloumns: type, kind, val.