Yeah, but as I see that is not the only problem. As I see it you are trying to reach perfection immediatly. The trick here narrow the scope a little and what is the absolute requirements for success and what requirements are for perfection. You are looking into this problem with "We need to do this fast, there should be no bugs and it should also be easy to make faster(or keep performance) by adding X! oooh did I mention that it should be easy to maintain? Because bugs will occur, it does not always work faster(or keep performance) when you add X and we should also be ready to add feature Y within the deadline because we missed it when we started."
IMHO you need to focus on people that can produce maintainable code first, because out of that the individiuals in the team can derive high-quality and scalable code.
Also you can't do anything about the quality of the code if you don't know where quality lacks and you can't do anything to the scalability and performance of the code if you don't know where these issues are. And you'll have no chance of fixing them if the maintainability of the code lacks.