> everyone keeps coming to you to name things Nah, not really. Years ago when we worked in office and I was still a junior we did discuss naming things here an

> everyone keeps coming to you to name things Nah, not really. Years ago when we worked in office and I was still a junior we did discuss naming things here and there but I didn't like those conversations. It's all just opinions and habits. > you're in a pocket of devs with high verbal skills I mean, we don't hire juniors so it's possible but doubt it. > you're in an echo chamber where everyone is equally bad Most probably but if no one is having problems with reading code then I'm not sure what bad even means. If it's in English and it describes what it does and does not use any tricks - it absolutely doesn't matter how exactly is it worded and structured. The examples from the article are especially bad. I've seen some code I'd consider bad in general but it was all about those library hacks (usually ORMs) I mentioned previously or about trying to fit a lot in a single LINQ statement (i'm a c# dev). The only time when I'd consider naming to be bad was were all variable and function names were in German. > There's literally a programmer joke about how hard naming things is. It's a joke because it's not that serious. It might be hard sometimes to come up with any name for a thing (especially for non-english speakers like me) and you plop down a "var x" or something even less mature and run which is funny. So it is hard but it's not a "real" problem.