title: Using generic columns in a database - why?
body: <p>I'm working for a company where our design team has elected to use "Field1".."Field10" as generic, future purposed columns. I have queried them as to the reason and was told that they are there in case we need them in the future.</p>
  
  <p>Has anybody heard of this practice? Is it wrong for my jaw to drop to the floor when I see something like this?</p>