However, I think that a Bachelor's degree is supposed to be about something other than job training. Sure, there is some overlapping material between "prepare for a job" and "get a Bachelor's degree," but not very much. People who have a Bachelor's are expected to have knowledge that is both broad and deep. That is, they are expected to know far more than they need to know, and have skills outside of their area of expertise.
Not that there is anything wrong with your approach, I just think that it disagrees with the overall goals of a standard university degree program, which is not terribly concerned about job preparation.
If you can just copy and paste answers, with source, then you haven't actually learned anything (technically, you might have, but there is nothing in your work to support this conclusion - unknowledgeable until proven knowledgeable). The grade you receive should be a measure of the skills you have obtained, and the things that you have learned, rather than the results you produce. Sure, you can do this in the real world, but in the real world you are not trying to show what skills you have obtained, you are only asked to produce results - this is the major difference between the education environment and the work environment.
In the real world, you do get punished if you need to program something, but don't know how to. College CS classes aren't meant to teach you how to get stuff done using software, they're meant to teach you how to program. Handing in someone else's code is not going to accomplish that.
I think that works as enough of a deterrent to what you suggest whilst allowing students to get on with making interesting projects and not reinvent the wheel.
>> In the real world you don't get punished for using Google or surrounding yourself with people who are smarter than you.
In the real world, you are generally working on a problem that has not been solved before, so although you might find a few snippets to learn from, most has to be created from scratch.To emulate the real world, each student or team has to have its own problem. This is possible (as discussed in the post), but raises the level of effort for the instructor considerably.
Maybe classroom programming shouldn't punish you either. What if you could turn in any code you wanted as long as you cited where you got it from and which license it was released under?
// got this from John. he explained this to me & now I finally understand how it works!
or
// thanks Google! found this great code on Github (Apache 2.0 license)
Of course, this approach would require assigning different types of projects than we're currently used to, but I imagine students would graduate a lot more prepared for real jobs.