title: Lookup Tables Best Practices: DB Tables... or Enumerations
body: <p>If we have to store the available positions at a company (i.e. Manager, Team Lead, ... etc). What are the best practices for storing it? I have two opinions with comments... "sure, welcoming yours"<br/>
  <b></p>
  
  <ol>
      <li>Storing it as DB table with columns ID and Name, and deal with it using queries and joins.</li>
      <li>Storing it as Enum and forget about the DB table.</li>
  </ol>
  
  <p></b>
  In my opinion, I will choose the first solution if I have changing items. So that I won't hard code these options as Enum.<br/>
  I may choose the Enum solution, if I have no doubt that data won't change (for example, Gender: Male, Female). <br/><br/>
  <b>NOTE:</b> I code in English, and the UI Culture may be Arabic. If I will work with the Enum Solution, I will hard code the culture-based strings in the presentation layer, is it okay from the best practices perspective!!!! <br/><br/>
  I would like to know your opinions and if my thoughts correspond to what is most recommended "Best Practices"?? </p>