I like the "computational thinking" concept for computing literacy that doesn't imply being a professional programmer, as described in this article: http://www.

I like the "computational thinking" concept for computing literacy that doesn't imply being a professional programmer, as described in this article: http://www.cs.cmu.edu/~wing/publications/Wing06.pdf http://www.cs.cmu.edu/~wing/publications/Wing06.pdf Familiarity with those concepts might help bureaucrats with organizational planning even if they never wrote a line of actual computer code. Programming is first about making things so clear and well-understood even a computer can handle them, and only second about actually making a computer do them. Atwood might have a point in that if someone just goes off to learn to code using a cookie-cutter course, they might not really learn to work with the more important first part, but might end up like a JavaScript programmer who has no idea about Turing-completeness instead: http://reddragdiva.dreamwidth.org/579047.html http://reddragdiva.dreamwidth.org/579047.html