That's basically the goal, that we can create cheap code domestic instead of sending the work abroad. What good that would do, well, you can divine by gauging the quality of code you get from abroad.
In the end I can reassure you that it will not work out. Programming is not just a skill you can pick up by drilling it into the heads of people. It's at the very least as much dependent on a certain state of mind (lacking a better term). You will certainly create a few people who will be more or less capable of slapping together some code, mostly in a cargo-cult, copy-paste fashion. And their programs may actually work. Sometimes. And that "sometimes" is exactly the problem. Because these people don't know how to take special cases into account in a way that they don't fuck up the result.
And this is critical. Because the main reason companies want to use computers is to create results fast and without human work. And that entails that it is mission critical that you can rely on the results to be correct. Because if you can not, that advantage you want to get is null and void because you still have to put a human there to at the very least check the plausibility of the results, and in the end you might end up with wrong results which can be VERY expensive to clean up afterwards.
And that's the huge problem here.
With many other things in life you can hire cheap amateurs and if they fuck up, you notice it quickly and can fix it. If your plumber fucks up, you notice it quickly with the huge puddle forming in your basement. An electrician creating a mess usually means that the power is gone. Hopefully nothing worse. A programming error may surface after years, leading to costly all-night repair sessions from experienced programmers who tend to cost an arm and a leg. A security hole in a software you use can easily lead to even worse damage. And again, damage you might not notice until it is far, far too late to mitigate it.