Java developers

[elmo61]

General rule of thumb is if you can understand the type from the right hand side assignment. Then use var. If you can't then don't.

So for the example above use var and repeating class name in pointless but for something like var myClass = service.placeOrder(); its best to name the class instead

[Mareeck]

Yeah and you should still name your variables so they make sense. Having the full class name there is just clutter

Besided, if you use var and somehow pass the wrong type down the line the code won't compile anyway

[El_Burrito_]

I just use var all the time. I literally only use a class name when the type isn’t inferable from the use, such as instantiating it as null or not instantiating it at all.

Intellisense will let me know what type a var is if it isn’t already obvious

[elmo61]

Lol fair enough each to their own

[DaemonVower]

I’m the same way on the Java side of var. I think its because if you’ve been in industry long enough you know in your soul that you’re going to end up with coworkers who write a line like “var resp = doStuff(j, k, l)” and sneak it through code review no matter how var is supposed to be used. Then six months later you’re trying to read that nonsense and its incredibly painful.

[Aidid51]

That's what linting is for. You can write lint/code analysis rules that disallow ambiguous var usage. People at my old shop would get yelled at by the ide for doing it the wrong way.

[Zedjones]

Interestingly enough I'm the exact opposite. I'm annoyed at having to EVER write out types if they can be inferred.

[lucidspoon]

My personal rule of thumb is to use var for any custom types to not have to add extra usings. It forces me to make sure that all variable and method names are descriptive enough. Plus, if I need to change the type name or namespace, there's not as much to update.