4 ms·
Many good comments here already. One thing about the "computer literacy"-thing -- I think that's elevating the standard a bit. I prefer "computer use", as in "w
by e12e 10y ago
Many good comments here already. One thing about the "computer literacy"-thing -- I think that's elevating the standard a bit. I prefer "computer use", as in "we need to enable people to use computers". Sure, "computer literacy" covers that, but I think it obscures how bad people are at using computers. Even young people that have grown up in a world surrounded by them.
I routinely work with people that can't leverage a spreadsheet as a better calculator - and prefer the "calculator app" for help with arithmetic. Now, I know that it's easy to fall back to using the first thing/tool we know - a hammer for every screw, so to speak.
But I think part of teaching how to actually use computers, should also be teaching people to look for the better tool, or to be able to make one. Much like how Bram Moolenaar, creator of the vim editor, talks about constantly looking for things we do while editing that is repetitive, and probably could be improved (either by discovering/looking up functions that are there, but we don't use day-to-day, or by scripting) - so it is with all things we do on a computer. It's in many ways the ultimate tool for data and information - everything can be (more) automated. If we have the right mindset, and mental tools.
In my mind, that's what "computer literacy" is about, and basic programming is absolutely a part of that. While I'd prefer to see people know how to write a python script to find their way out of a wet paper bag, even if we just enable 80% to actually automate spreadsheets, that could have a huge impact on overall productivity. Because despite the horrors many hn'ers probably have encountered in terms of visual basic, access and excel -- still far too few people are able to make such horrors in order to do everyday tasks, like sane shift scheduling.
I think we need a bit of a revival of the ugly, everyday scripting and maybe even so called "4gl" languages -- because while they often are the wrong tool when you want to make a shrink-wrapped tool for others to use (maybe even something you could sell), I think it is often very much the right tool for thinking, experimenting and making certain tasks easier and less error prone.
As a side note, a sane spreadsheet-like interface with a sane programming language would probably be a good idea. R does this to a certain extent, but I'm not sure I'd want to try to use R to plan shifts, or do a number of arithmetic things like manage my budget or calculate material use for a circular stair case and so on. I'd probably prefer something like Python or Ruby coupled with something a little snazzier than a CSV-file (ok, I would totally prefer grep, awk and a text-file -- but I think we should be able to do better).