4 ms·

I understand the idea, but it requires: * great ability at naming methods - which isn't very common * massive discipline at RE-naming methods when they get cha

I understand the idea, but it requires: * great ability at naming methods - which isn't very common * massive discipline at RE-naming methods when they get changed even slightly to do something more Regarding the latter, I've seen so many times methods which originally described what they were doing, but now they don't any more, that I never just trust the name to tell me what a method really does.

catlifeonmars 4y ago
Naming is probably the single hardest part of writing scalable, legacy code. Cache invalidation is a cakewalk in comparison. I believe this is in part because naming is a miniature exercise in empathy for future readers particular of a piece of code.