First of all, could someone enlighten the non-US readers about what common core is? I hear the term a lot, not clear what the main ideas actually are or how people view it. My own kids go to private schools in the UK. None of the parents would have any problems buying a load of tablets or VR goggles or whatever if the schools said so, and the schools would not have any problems buying whatever manner of gadgets they…
A new set of standards for education that are meant to cut across state lines (e.g. California and Texas previously set education standards merely through market volume and being the biggest purchasers). It's mostly fine.
A lot of people are upset that they "changed how math works" but what they really did was introduce a bunch of different ways for students to think about math so they can get a working math literacy. Instead of being a prescriptive standards ("this is how math works") its more descriptive ("here are a dozen ways one could reason about math to get the answer"). The hope is that this will allow students to better pick up and understand more advanced math in the future, while also providing more opportunities for struggling students to "get it" (e.g. because one example worked for them).
> As a programmer I'd love it if the kids could learn some of what I do, and there's plenty of interest, but essentially the article is right. The point isn't to make little workers who can write an insertion sort. If you are educated, and you wind up in a place where that's needed, it won't take you all that long to figure out.
I think the important thing, instead of learning how to program insertion sort, or even to program (except perhaps as an extra class), is learning how to reason about basic computing ideas.
Explaining basic ideas like Turing Completeness (and the related ideas of no way to control how another device does things impacts on sharing always meaning copying is possible), NP Hardness (allowing people to reason about how computers actually work, it can only brute force and do clever math, what it can and can't know), cryptography (trust and privacy), and what software engineering vs. programming is (like, discuss the size of code bases, where bugs come from, programming as vocational skill like cooking or writing that is also useful in other fields, etc).