3 ms·

As I said, highlighting of identical words helps a lot with that. Example: https://code.visualstudio.com/images/language-support_document-highlights.gif https:/

• jstimpfle 10y ago
  IMHO something is broken with these guidelines and the IDE's we have. Isn't this a contradiction? On the one hand it is argued that long variable names are needed to improve readability. On the other hand tools are needed to read the resulting mess. I've had to develop team codebases in both Eclipse and Visual Studio, and the experience was not good. Not only were the IDEs slow and buggy, but also the code (which followed the long names cult) was terrible to work with. No cohesion, no separation of concerns. Personally, most of the time I'm happy to use vim without any plugins. Most time is not spent typing, but thinking about factorization of the program. Depending on scope I mostly use short variables. I don't expect to be able to dive into code without understanding the context -- the idea that this is possible is a misconception. But it could very well be that the people arguing for long names do e.g. business code (where concepts might or might not be less clearly scoped and cohesive) and people arguing for short names do e.g. more algorithmic code. Without proper scope (ha!) this discussion is worthless.