I think this what people really are looking to stop: "Tim just got a new phone. Tim needs his IT friend/family member to help him add wifi to his phone. Howeve

I think this what people really are looking to stop: "Tim just got a new phone. Tim needs his IT friend/family member to help him add wifi to his phone. However, by help, Tim hands the friend/family member the phone and now it works!" Like others have said, the layman wants "computer science", but really wants "computer literacy". Phones, software, technology changes so fast that current teaching methods become outdated in years (I'm looking at you Intro to Computers classes). As computer literate users, we get you go to "Settings" and poke around til you see something like "Network" and then something like "Wireless" or "WiFi" and are set. However, would I do this same behavior with a car? Pop the hood and poke around? Computer Science seems like the route to people because of the side benefit of "figuring it out on your own" comes naturally after 3 weeks of programming. Don't understand something? You have to pool every resource you have (instructor notes, slides, books, websites, etc.) to 'get' it. And even then its not an 'AHA' moment. Its a pray and 'whew' when whatever you did works. But somewhere along the way, most programmers pick up that 'it', that computer savvy-ness that people are looking for. They want to stop being dependent on IT people because all we do is huff and puff about how simple a task is (regardless of program, if someone asked you how to bold text, how would you get them to bold the text WITHOUT pointing at the screen?). Personally, it doesn't have to be "learn computer science", but it needs to be a complete redesign to the "Intro to Computers" style class.