>>You could go on forever but really it just boils down to someone making bad decisions from inadequate knowledge and lack of foresight. > To what level should

>>You could go on forever but really it just boils down to someone making bad decisions from inadequate knowledge and lack of foresight. > To what level should a developer be at before joining the workforce? > How do we bring all potential developers up to this level so that we can have a smarter workforce? > Can you create an education system that reliably produces developers at that level? The solution is really to give junior developers a level of responsibility (and feedback) that matches their level of experience. Juniors shouldn't be making architectural level decisions or even major design decisions, nor should they be deciding _what_ to build. They should be receiving feedback on the small-scale design decisions they do make, and exposed to the senior devs' decision-making processes so they can develop that level of knowledge. And their responsibilities and exposure to business goals and impact metrics should be gradually increased as they gain the experience to be able to make larger and higher-level decisions.