title: Naming convention for List variables
body: <p>I have a question that may seem pretty trivial to many, but it's one that has made me think repeatedly about the readability of the code that I write.</p>
  
  <p>Lets assume that I have a class that encapsulates details of an entity, such as an employee, called <code>EmployeeDetails</code>. (Note - I also have a class named <code>Employee</code> which exists at the DAO layer. I do not want to return any DAO level classes from my service methods, which is why I created the <code>EmployeeDetails</code> class to be returned from my service layer methods. I also wanted to avoid confusion between class names by keeping the service and DAO layer class names distinct).</p>
  
  <p>I also have a service level method that, given a list of Employee numbers, returns a <code>List&lt;EmployeeDetails&gt;</code>. My question is this - what is the best coding convention for naming the return variable? I had two options in mind.</p>
  
  <ol>
  <li><code>employeeDtls</code> - I do not like this because the person who reads my code may think that "employeeDtls" refers to an instance of <code>EmployeeDetails</code> instead of a list.</li>
  <li><code>employeeDtlsList</code> - I do not like this because it seems "too wordy".</li>
  </ol>
  
  <p>Does anyone follow any specific coding conventions for variables? What is the most widely used naming convention for list variables?</p>