The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
The problem is that it sometimes becomes a style guideline in teams. I have seen that happening before, which is just stupid to me.
"Oh, but you can just hover over it and you will see". This mindset can be a real nightmare on code reviews.
I hate the laziness that motivated most var uses I have seen. People don't even know why var was created (to support anonymous types).
There are though, as some people have already mentioned, some situations where var makes the code cleaner. But I actually never seen that kind of diligence, so wherever I could I abolished the used of var for non anonymous types.
To make matters worse, stupid resharper (that some people like to use) has the default setting that everything should be var. So it pretty much converts the new-comers to the var mindset from the start.
To alcohol! The cause of, and solution to, all of life's problems - Homer Simpson
Our heads are round so our thoughts can change direction - Francis Picabia
In my experience, the need to use var arises from wanting to hide the sometimes lengthy names of collection iterators in foreach declarations. Especially when Linq is used to get the collection, the declaration can become messy.
But you now how it goes: first it's to shorten lengthy iterator names, then lengthy class names, then pretty much everywhere because it looks more consistent for some people.
I can support the use in foreach declarations, but everywhere else it's more of an annoyance.
I never understood the desire to hide stuff like this. It's like an unspoken commitment to never refactor whatever is hidden.
There is no advantage. If you just write a scribble, then always using var is Ok. But if you write production-level code, var is sloppy style and thus an absolute no-go. Before IntelliSense was able to automatically convert the var's in your source code to the correct type, var was even an evidence of a programmer not knowing what type they're using.
Only exception: Use var to avoid writing the same type twice in the same line.
List<string> list = new List<string>();
var list = new List<string>();
Because then, when you want to change the type, let's say from List to HashSet, you only have to change it once. IntelliSense also suggests this, at least in VS 2017.
I threw 'of all' in there as a little red herring to add a little ambiguity as to whether the target word was ALL or ETYMA. Connector words are generally allowed and have nothing to do with the cryptic meaning.
I was taught that line graphs should only be used for continuously varying data, whereas bars should be used for discrete values. In this instance the time spent per day is a discrete measure (unless maybe you're working a 24-hour day) so bar is "correct". Whether pie or bar depends on whether it's the ratios of the different types or their absolute sizes you want to illustrate; though it's possible to show both in a pie chart by having different sized pies, of course.
Options are available. Always. And they can be counted. And they can be numbered. And the user can choose them by their number. And it shall be good.
Easy pill to swallow, options.
Thank-you Dr. Nefario!
Oh, and I forgot something. Each interface shall have it's own help tome associated with it's use. And that extensive collection of non-video tutorial pages shall have images upon which one shall be able to hover with one's mouse and receive more information in contextual text message. And clicking upon sub-image locations one shall be directed to pertinent and whole help pages where related images reside and they shall be contextual as well. And there shall be no advertisement. And then the most good shall come in the final help file link where searching might be done in non-indexed suggestive search-in-search returns so that it shall be possible to find that one words meaning so that it shall rule all meanings.