[dcole2929]

I agree with the author here in principle. Being able to parse out what someone actually wants from what they ask for is key in pretty much any business type interaction. And as the author argues what is often the case is that people want to learn how to build something not Computer Science.

I have a sister in eleventh grade (16-17) who is interested in programming. But if I tried to teach her programming by going straight to data types and algorithms her eyes would glaze over. That's not say she is dumb or traditional CS education is hard but it's certainly not the most interesting of topics.

However I think the argument against starting by building things the author barely even glosses over. The ecosystem and tooling to build things has become so complicated that it makes it hard to start. Someone just learning programming is probably going to be bored to death by ints and bits, but they are likewise going to be equally discouraged by the amount of work outside of coding it takes to get any non-trivial web app up.

And honestly the same goes for mobile development too. It's slightly less ridiculous but then you run into the issue of things that can't be explained simply and get relegated to "magic" you don't need to worry about... until you do.