When we say we want kids to code, we're saying one of two things. Either we're saying that we want them to learn a skill that will offer them employment, or we are saying that we want them to become familiar with the logical constructs that go into coding.
Welcome to almost every conversation with a prospective undergraduate, their parents, and unfortunately many, many post-secondary educators (I differentiate that from one smaller subgroup called "professors"). Welcome to every conversation about humanities and technology degrees and curricula (eventually leading to—dun dun DUNNN—digital humanities). Every disciplinary conversation about film, web design, etc.
One counterpoint, in my opinion not sufficiently addressed in this essay. Understanding only the most basic constructs, and then lobbing ideas down at underlings, contractors, grad students, employees to let them handle every detail that is not from a stratospheric point of view does not make you a "maker" or "designer." It makes you a manager.
Addendum: Cecil Decker wisely wrote "is there something wrong with being a manager?" Definitely not. Nothing inherently wrong at all. I do a lot of manage-y work in my job, and it's a completely different set of skills than making things, or teaching.