title: If a "Utilities" class is evil, where do I put my generic code?
body: <p>I generally live by the rule that Global variables / functions are evil and that every piece of code should live in the class to which it pertains.</p>
  
  <p>This is a very easy rule to follow, and I believe that I haven't ever run into an issue with this rule until now.</p>
  
  <p>Today, however, I need to add a function to my <em>assembly</em> rather than to a specific class.  That is, almost all of my classes <em>could</em> have a use for this particular function.</p>
  
  <p><strong>Where should I put this function (+1 overload)?</strong></p>
  
  <p>If I put it in a "Utilities" class, I feel dirty.  If I tack it on to a semi-related class, and let other classes call it directly, I feel worse.</p>
  
  <p>This particular piece of code basically chops a <code>IList&lt;PointF&gt;</code> into a normalized list.  I feel right now that adding it as an extension method on <code>IList&lt;PointF&gt;</code> may be the best bet...</p>