title: What is the point of the lower camel case variable casing convention (thisVariable, for example)?
body: <p>I hope this doesn't get closed due to being too broad.  I know it comes down to personal preference, but there is an origin to all casing conventions and I would like to know where this one came from and a logical explanation as to why people use it.</p>
  
  <p>It's where you go all like <code>var empName;</code>.  I call that lower camel, although it's probably technically called something else.  Personally, I go like <code>var EmpName</code>.  I call that proper camel and I like it.</p>
  
  <p>When I first started programming, I began with the lower camel convention.  I didn't know why.  I just followed the examples set by all the old guys.  Variables and functions (VB) got lower camel while subs and properties got proper camel.  Then, after I finally acquired a firm grasp on programming itself, I became comfortable enough to question the tactics of my mentors.  It didn't make logical sense to me to use lower camel because it wasn't consistent, especially if you have a variable that consists of one word which ends up being in all lowercase.  There is also no validation mechanism in place to make sure you are appropriately using lower vs. upper camel, so I asked why not just use proper camel for everything.  It's consistent since all variable names are subject to proper camelization.</p>
  
  <p>Having dug deeper into it, it turns out that this is a very sensitive issue to many programmers when it is brought to question.  They usually answer with, "Well, it's just personal preference" or "That's just how I learned it".  Upon prodding further, it usually invokes a sort of dogmatic reaction with the person as I attempt to find a logical reason behind their use of lower camel.</p>
  
  <p>So anyone want to shed a little history and logic behind casing of the proper camelatory variety?</p>