Lessons Learned: Please teach kids programming, Mr. President
startuplessonslearned.blogspot.com
startuplessonslearned.blogspot.com
If the author here really cares about what he's saying he should write a lesson plan that teaches programming and send it to schools. Put up a website that asks for support of his lesson plan. Solicit donations for computers in classrooms. Overall just get off his own @$$ and try to make it happen.
Finally, I don't see what DRM and banning Cell Phones has anything to do with teaching technology to kids but I can say his first point is largely wrong. I grew up in public funded housing (aka the projects) and even we had computers in our classrooms. If someone can find me the high school that is completely without computers in the U.S. I'd like to see it becasue I think it's just a myth.
I'll take your suggestion a bit further--I think, instead of looking to the government to implement these changes, why not provide an opportunity for bright kids to opt out of the current system? Enable cooperatives and networks to provide the kids with environments that will them flourish.
I've started taking lecture notes on my android phone. Its surprising how having an open phone and a decent keyboard makes you rethink the amount of computing power you carry around in your pocket.
I recently went to a seminar on pervasive computing where one of the speakers demonstrated that audience members could learn to type accurately on a chording keyboard without looking at the screen. I was going at 25-30wpm already by the end of the lecture. A cheap bluetooth version would make subtle notetaking really easy.
Most people are doing fine and use the computers without knowing how to program and I drive a car and don't know how to build or repair one. To prepare kids for technology teach them science, logic and math.
I mean, we don't teach circuit design to everybody, on the sensible principle that most people will never design a circuit. But we teach the anatomy of worms to everybody because... most people will eventually have a pressing need to dissect a worm? I mean, I'm not the world's most accomplished programmer by any stretch of the imagination, but I very rarely get asked by the bosses "Hey, Patrick, after you get done with that Javascript, could you please pull the heart out of the worm on my desk?"
I was also forced as a child to learn about some rocks floating around in the general vicinity of the sun. I still don't know why these rocks matter -- my best guess is that pre-modern civilizations thought they were gods, poets picked up on it, and people now consider the notion of travel to them sort of romantic. I'm at a loss as to how learning about rocks prepares one for programming, unless one aims to be one of the few hundred programmers engaged in writing software to control missions to space aimed at getting ever-more-detailed photos of the rocks "for scientific purposes".
Ditto lab chemistry. Titration is a) technician work -- its a repetitive process with about as much intellectual content as swapping hard drives which b) will be performed by perhaps half of a percent of the population in their lives, if that. Yet we make everyone do it. It makes about as much sense as making woodcarving mandatory for everyone... because you never know, right?
Let alone intellectual curiosity.
Don't teach kids, inspire them to learn instead...
http://www.amazon.com/Mindstorms-Children-Computers-Powerful...
http://www.amazon.com/Structure-Interpretation-Classical-Mec...
http://www.amazon.com/Turtle-Geometry-Mathematics-Artificial...
This is not to mention that learning how to program a computer is just another tool to put in your bags of tricks for solving problems in any of the domains you mentioned (some better suited than others, of course).
No because the sample is biased. People who read stackoverflow are nerds and more incline to have begin programming early and mid-career starters are more incline to not read it.