title: Entity framework - Code First - Is it really good approach for big projects?
body: <p>I have been doing some reading on code first approach of the entity framework and the other approaches(Model first, database first). </p>
  
  <p>1.)The reason supporting entity framework code first approach in  a lot of blogs seems to be to keep developers happy so that they dont have to work with designers. I am suprised at this argument because, you develop a project to keep your customers happy and not your developers. How many projects out there have developer happiness in the project plan. Another argument is to avoid a lot of mappings on xml. Well, if not xml, we end up doing that anyways in OnModelCreating and adding [Key] attributes to domain models. So mapping is not eliminated. </p>
  
  <p>2.)Also when you generate a database from the code(domain model), the domain model is designed in an OO way and the generated database structure might not be the optimal one, which forces me to think that this code first approach is only suitable for small projects. </p>
  
  <p>Are arguments correct?</p>