Consider math. It's extremely useful and people need it to properly function in modern life. And yet people are not only terrible at it, but they are proud of how terrible they are at it. They believe (incorrectly) that math is something you "just get" and that it is not a skill that can be learned. To me, those people are illiterate, but the perceived social stigma of being math illiterate just isn't there like it is with actual illiteracy.
So, if math, which is much more fundamental and useful in the every day lives of people isn't the new literacy, I don't think coding has a chance.
I think this statement is only accurate for basic math. Nearly everybody I've known has had a situation where they wanted to code something or wished they knew how. Math is almost the opposite, I've heard more complaints about wasting time on "useless math" than I've heard regret for not pursuing it more. That's not to say they're right, but it's absolutely a strong opinion I've heard from a huge range of people.
I do disagree with the premise of coding being the new literature though (as defined by >99% of the population). Any point where that percentage is reached will be one where programming looks nothing like it does today and has been abstracted to a meaningless level.
At a fundamental level, math is taking stuff you know and manipulating it into answers to stuff you don't know. That thought process is extremely important. I use it every single day. Sometimes it's intuitive, like saying, "I need to visit five stores today. What's the most efficient way to get there?" Other times it's actual math, like saying, "I need to figure out the most efficient way to tackle my debt."
The list goes on and on. Can I justify buying a new car? Should I go to college? If I were laid off tomorrow, how long could I support my current lifestyle? Even questions that have nothing to do with math such as "How do I replace my brake rotors" require that exact same mindset. Start with the stuff you know, and use it to get answers.
Will you use integration by parts in your job? No. Will the thought process you've cultivated by applying integration by parts on a difficult problem help you? Yes, vastly.
If you don't know math, you might not realize that a lot of these questions have concrete answers that are relatively easy to figure out. You might just wing it or not bother at all. And while that's perfectly fine when you burn another quarter-gallon of gas on your errands, it's not when you're figuring out whether you need to sell your car or how much to save each month for your kid's college fund. Or when you're given shady statistics by a politician. Or when you're offered the Once In A Lifetime opportunity to invest in Amway.
http://mysite.science.uottawa.ca/mnewman/LockhartsLament.pdf
Are computers everywhere and do people use them every day? Yes. But mechanical ability isn't the new literacy and just as many people interact with engines on a daily basis and would be helped by it in daily life. I think it is much more useful to think of programming like woodworking, leatherworking, sewing, soldering, etc. Very useful skills which can improve your life, but not at all necessary, and "only a few people only need to be really good at it" as you stated.
Literacy itself used to be a niche skill, learned by a select few who made an earning from it (scribes, criers), while the majority of craftsman got along just fine without it. Then the printing press came along, and it brought a proliferation of readable material, and literacy became useful. Not essential, but useful. People could distribute political literature, or send messages cheaply. Literacy bloomed. And as literacy increased, and became expected, it became essential.
We're at the beginning stage of that now. Somewhere around (probably before) the printing press. Programming literacy is becoming useful, but not yet essential.
I have a lot of friends who work in offices surrounded by Excel spreadsheets all day. I know for a fact they would be more productive if they knew how to use it better, write macros, VBA... or heaven forbid, use a database instead. I think this is going to happen more often in the future, too.
Stupid alert: I briefly worked at a startup that did push to production by remote desktop to the server and manually restarting the IIS server after copying things into place. They didn't automate it - because "it's the way we always did it." (Yes, they're out of business now.)
Automation also has the potential to make a task less error-prone and its output more consistent. A botched or forgotten manual task can be difficult to clean up after, so there's risk management too. For instance: in one incident, a coworker at a former employer accidentally ran the "send thousands of people email about how much we're about to pay them in a few days" script on input from the wrong year because January had just ended and he had to input a value containing the last day of the month (e.g. 2013-01-31) by hand.
That is, if the benefit is worth the costs.... do so. Otherwise, reconsider.
And few things make as glorious as a mistake as an automated job going out of control. There is a reason one of the most important questions you should ask on any automated task is "how do I make it stop?"
There will always be a need for people who understand computer science, but those engineers will be like compiler engineers or hardware engineers are today...enabling a much larger group of programmers to produce the software that provides value to users. And as we're able to provide improved layers of abstraction to make software development easier, we'll see computing become more accessible to more programmers who will build software with a much richer understanding of the domain.
So I'm torn about initiatives like this. I see coding as the new literacy...it will be a skill required by almost every professional who is an expert in his or her domain. But they won't be coding in today's languages and coding will be significantly easier than it is today. So we need to find a way to teach children to develop using tomorrow's tools today. And that means extracting the part of programming in today's languages that is intrinsic to programming while doing our best to avoid the part of coding that is just pain inflicted by today's limited abstractions. That separation may be difficult (or even impossible) to achieve, but that doesn't mean we should try. Because anyone who doesn't learn how to instruct a computer to accomplish tasks is going to be automated out of a job (https://www.youtube.com/watch?v=7Pq-S557XQU)
That is an extremely unusual definition of "literacy."
"Coding is the new literacy" implies that coding will be necessary for anyone who wants to interact with modern life, not just for experts. Imagine trying to use the freeway system if you could not actually read streetsigns, for example. i.e. if you were illiterate.
That's the whole point. Computers and robots are creating a world in which there really isn't room for anyone who isn't an expert. We've already automated the low-hanging fruit...we've got a fraction of the manufacturing jobs because computers and machines can do that work faster, cheaper and more effectively. Google and such are working on less low-hanging fruit (people who drive automobiles for a living, lawyers...there's a bunch of examples in that youtube clip). That bar for offering utility beyond what can be automated is steadily rising.
If you're not an expert in something, you're going to be pretty useless in the world we're creating.
Managing the rapidly increasing number of computerized systems.
>our everyday systems are designed by an increasingly smaller group of people.
What are you talking about? Open source is bigger than ever. There are more computer scientists than ever. I can't think of a context in which this statement is true.
You might say "that's absurd, Twitter, Facebook and email aren't going anywhere!" -- but look at What's App or Snapchat or any other communication medium.
There's always room for improvement. Most solutions might be awful but every attempt to improve a system carves more of a path for the next giant.
Regular expressions and basic Unix utils are also amazingly valuable in non-tech jobs that involve computer use.
"Life skill"? Maybe not. Enormously valuable in bureaucratic jobs? Definitely.
The point of bureaucracy is not to be efficient, it's to give jobs to people who otherwise would be flipping burgers or mopping floors, but are too educated for that. See hyper-bureaucratic countries like France for a vision of this.
I'm on the side of basic income for everyone to avoid this problem and reclaim efficiency in administrative processes, but in our judeo-christian cultures not working is considered a bad thing®, and thus this idea has a hard time gaining traction.
This is one of the lessons that keep cropping up when they try to automate say claims administration at the VA. Something that's only 90% automatable might as well be 0%.
Is your assumption that businesses are thriving while wasting 10-30% of their revenue on busywork? If so, it should be trivial to crush them with your 10-30% reduction in overhead. Do it?
Is your theory that regulations requiring hard-to-automate bureaocratic work is created with the sly intention of creating busywork for people? Ah, special interests. They can lead to some messed up stuff, but most regulations are put in by well-meaning people trying (often ineffectually) to do what they're actually stated to be for--enforcing safety, fairness, etc.
I've regularly stated that I want most of my job automated away by Google, and we do have start-ups chipping away at old business models, but if it were entirely a matter of simply deciding to stop wasting money, I'm going to go out on a limb and say someone would've done it already.
However, I suspect that coding will become the new literacy. It's becoming an essential life skill, but only a few people need to be really good at it; most people just need a basic functional knowledge.