Me too. But that's also what makes me uncomfortable when reading this article. Proper Naming is truly an "art" of balancing trade-offs. It takes domain expert

Me too. But that's also what makes me uncomfortable when reading this article. Proper Naming is truly an "art" of balancing trade-offs. It takes domain expertise (Ubiquitous language), understanding of the users of the code (other devs, not end-users), and a lifetime of coding f*ups where naming something wrong turned out painful to balance these. The author gives a nice example of a dynamic table naming. But their refactoring didn't keep the behaviour the same (the else/catch). So it's hard to argue the first is better. And in this case, even without the else/catch, I'd say the latter is better. But there will be cases where greppability is to balanced with readability, testability or refactorability. And in these cases, for me, greppability comes last.