uAren_tWong
It's fairly logical, actually very logical, inasmuch as it is to think that the human mind can process things in some discrete amount, and then move that data to the hindbrain and ready the visuo-spatial cortex for more.
Repetition is key for this to happen, yet we don't really reiterate a lot (well, in my humble experience) of the things we learn as CS students, other than the bajillion attempts to code properly on our own. We do things maybe twice, three times, then we take some notes or move on to a different part of the subject. The brain needs a 'lot' of repetition to have something down like we do things that require muscle memory.
So, how to make something that would, on its face, appear tedious into a feature set?
Well, again, from my humble teaching experience, and to extend the muscle memory analogy: muscle confusion!
Mix up the media used to teach, and be creative about it. Don't just copy paste a slideshow from a dataset that some UW prof has put together, and then add a video from a YouTube tut, and call that a multimedia presentation (no offense, I know teaching is fucking hard, I'm being ideal here). Instead, MAKE UP a cool little ditty about what constitutes a class declaration (punny, no?) and then couple that with a dance that entails the two dancers to be logical constructs like XOR and NOT and have a little memory register ho-down...lol.
Ok, well like I said, muscle confusion, but with the various lobes of e mind being entertained and enervated, booooi (said to the voice of Flava-Flav).
IF in doubt, simply go piece by piece, building larger chunks of data for he students to learn and reiterate over each new chunk aggregating the last until the entire set of concepts is learned well enough to be determined comprehensive.
If that is so, then the vulnerability described is likely to be an issue, perhaps later, perhaps sooner, but within some given time frame during which the ubiquity of the 'net will be ever expanding.
Perhaps the solution is to guide the users in some very 'user' friendly adaptation of a 'man. page' that describes with elegant confidence the methodologies germane to creating a keycode that would allow for said 'users' to give themselves the safety from the perchance nefariously driven 'code poets' who would otherwise be able to derive social insecurity from whatever access might be available to them.
Long winded reply to say we need to not think about stoppping using Linux, but instead use a nice little intro for those who don't know enough (or even very little) regarding how to code a patch in their own kernel.
Given that the tech will be integrating NLP more and more, I could even imagine a 'talk through' with some 'Ask Jeeves'-esque personal assistant.
The whole thing is essentially a trust issue. Who's writing the code and who's debugging it to give all of the nUbs (yes, I use the old abbrev.) enough insight to give a little polish and shine to their appliances and machines.
Whew, lotta writing there :d