# 9 Anti-Patterns Every Programmer Should Be Aware Of

<div dir="ltr">
  <div class="gmail_default" style>
    <ol style>
      <li>
        <font face="tahoma, sans-serif">Premature Optimization: Do not optimize too early before you know bottlenecks and problems in the live environment.</font>
      </li>
      <li>
        <font face="tahoma, sans-serif">Bikeshedding: Do not spend time on minor topics </font>
      </li>
      <li>
        <font face="tahoma, sans-serif">Analysis Paralysis: Do not analysis too much.</font>
      </li>
      <li>
        <font face="tahoma, sans-serif">God Class: Avoid big classes that control many other classes.</font>
      </li>
      <li>
        <font face="tahoma, sans-serif">Fear of Adding Classes: Add new classes if necessary and do not fear about the complexity.</font>
      </li>
      <li>
        <font face="tahoma, sans-serif">Inner-platform Effect: Try to use available features of your OS instead of re-writing them in your programming language.</font>
      </li>
      <li>
        <font face="tahoma, sans-serif">Magic Numbers and Strings: Avoid magic and undocumented numbers in your code.</font>
      </li>
      <li>
        <font face="tahoma, sans-serif">Management by Numbers: </font><span style="font-family:tahoma,sans-serif">Do not rely too much on numbers like LoC.</span>
      </li>
      <li>
        <font face="tahoma, sans-serif">Useless (Poltergeist) Classes: If class is not doing anything valuable, remove it.</font>
      </li>
    </ol>
    
    <div>
      <font face="tahoma, sans-serif"><a href="http://sahandsaba.com/nine-anti-patterns-every-programmer-should-be-aware-of-with-examples.html">Source</a></font>
    </div>
  </div>
  
  <p>
    </div> 
    
    <p>
    </p>