Fabio Franco wrote:

I blame ReSharper for the fever of using var everywhere.

Indeed! :| That's why I quickly felt pressured into using var. However, as with most things ReSharper, you can turn off the 'hint' in the ReSharper settings if the nagging gets too much and your employer's required coding style doesn't prohibit it. :-D

Interesting discussion. I found var a bit difficult to cope with at first as it does hide the actual type. Fortunately many IDEs will, as has been pointed out elsewhere, give you the type if you hover over the 'var'. This, however, doesn't help when dealing with printed/quoted code snippets or when working in an environment that doesn't reveal the type. So, my definition of 'appropriate' is where the type is obvious (usually because the assignment includes the type as part of a 'new' or a typecast of some kind) or because the type is so complicated that it obfuscates itself (e.g. nested generics with multiple parameters). In the latter case I either rely on VS for an explanation or, where possible, simplify the type by creating a new wrapper class/struct with XML help to explain what the class is about. The basic rule is "Think about other people when writing your code." Always ask yourself 'Can this be understood without having to look through reams of code or relying on an IDE to find variable/type definitions?' If not can it be simplified or explained?" If all else fails use a comment to explain (and thereby starts another argument :sigh: ).

Marc Clifton wrote:

If you don't like typing, why are you a programmer?

I'm a programmer because I like puzzles. Software development is usually the process of: 1. identifying the 'puzzle' 2. developing a solution 3. implement the solution with whatever tools you are given/have available Whilst 3 is still fun I don't want to write reams of code I don't need to so reducing the amount of code I type is fine by me. (Sorry for the boring answer to a hilarious rant :-\ )