title: Naming convention and structure for utility classes and methods
body: <p>Do you have any input on how to organize and name utility classes?</p>
  
  <p>Whenever I run in to some code-duplication, could be just a couple of code lines, I move them to a utility class. </p>
  
  <p>After a while, I tend to get a lot of small static classes, usually with only one method, which I usualy put in a <code>utility</code> namespace that gets bloated with classes. </p>
  
  <p>Examples:</p>
  
  <pre><code>ParseCommaSeparatedIntegersFromString( string )
  CreateCommaSeparatedStringFromIntegers( int[] )
  CleanHtmlTags( string )
  GetListOfIdsFromCollectionOfX( CollectionX )
  CompressByteData( byte[] )
  </code></pre>
  
  <p>Usually, naming conventions tell you to name your class as a Noun. I often end up with a lot of classes like <code>HtmlHelper</code>, <code>CompressHelper</code> but they aren't very informative. I've also tried being really specific like <code>HtmlTagCleaner</code>, which usualy ends up with one class per utility method.</p>
  
  <p>Have you any ideas on how to name and group these helper methods?</p>