title: How often do you see abuse of C# shorthand getters/setters?
body: <p>In C# you can create getter/setters in a simpler way than other languages:</p>
  
  <pre><code>public int FooBar { get; set; }
  </code></pre>
  
  <p>This creates an internal private variable which you can't address directly, with the external property 'FooBar' to access it directly.</p>
  
  <p>My question is - how often do you see this abused? It seems like it has a high potential to violate encapsulation best-practices often. Don't get me wrong, I use it as appropriate, and partial variations of it for read-only write-only types of properties, but what are your unpleasant experiences with it from other authors in your code base?</p>
  
  <p><strong><em>Clarification: the intended definition of abuse would indeed be creating such a property when private variables are appropriate.</em></strong></p>