>If you're learning a framework, you have the entire community - which has probably written blog posts, asked and answered StackOverflow questions, and likely h

>If you're learning a framework, you have the entire community - which has probably written blog posts, asked and answered StackOverflow questions, and likely has some members who can answer your question at odd hours. You're assuming that learning the framework will make understanding actual workload code completely effortless. In non-trivial applications this is never the case. You still have to understand... stuff like this, for example: http://mikehadlow.blogspot.com/2010/04/custom-aspnet-mvc-model-binder-for.html http://mikehadlow.blogspot.com/2010/04/custom-aspnet-mvc-mod... When someone writes code from scratch the quality of the code depends on their ability. When someone uses a framework the quality of the code depends on their ability, the quality of the framework and fitness of the framework for a particular problem. If the developer is not very experienced but sufficiently disciplined, and the framework is well-designed and fits the chosen task well, than yes, you end up with better code. If any of those conditions fail, the code is usually just as bad or worse than vanilla.