title: Lambda variable names - to short name, or not to short name?
body: <p>Typically, when I use lambdas, I just use "a, b, c, d..." as variable names as the types are easily inferred, and I find short names to be easier to read.  Here is an example:</p>
  
  <pre><code>var someEnumerable = GetSomeEnumerable();
  var somethingElseList = someEnumerable.Select(a =&gt; a.SomeProperty)
                                        .OrderBy(a =&gt; a.SomePropertyField);
  var someDictionary = somethingElseList.ToDictionary(a =&gt; new SomeClass(a.Prop1),
                                                      a =&gt; a);
  </code></pre>
  
  <p>Some question this naming, and would prefer to see long typed out names, like this:</p>
  
  <pre><code>var someEnumerable = GetSomeEnumerable();
  var somethingElseList = someEnumerable.Select(importantObj =&gt; importantObj.SomeProperty)
                                        .OrderBy(objsInfo =&gt; objsInfo.SomePropertyField);
  var someDictionary = somethingElseList.ToDictionary(theInfoId =&gt; new SomeClass(theInfoId.Prop1),
                                                      theInfoId2 =&gt; theInfoId2);
  </code></pre>
  
  <p>Since the scope is so narrow (between the parens), unless you're getting stupid and nesting them, I find it easier to read short names.  </p>
  
  <p><strong>Without getting caught up in the silly naming examples I used above</strong>, what is the general consensus on Lambda variable names?  To short name, or not to short name?</p>