title: What code metric(s) convince you that provided code is "crappy"?
body: <p>Code lines per file, methods per class, cyclomatic complexity and so on. Developers resist and workaround most if not all of them! There is a good <a href="http://www.joelonsoftware.com/items/2006/08/09.html" rel="noreferrer">Joel article</a> on it (no time to find it now).</p>
  
  <p>What code metric(s) you recommend for use to <strong>automatically</strong> identify "crappy code"?</p>
  
  <p>What can convince most (you can't convince all of us to some crappy metric! :O) ) of developers that this code is "crap".</p>
  
  <p>Only metrics that can be automatically measured counts!</p>