I agree with you, but this somewhat flies in the face of what he says. He is arguing that CS is important, not just learning to code. But I think learning to code is important because it is what attracts creatives, and both creatives and engineers are needed in development.
There are two things that attracted me to programming:
1. Telling something else to do what you want, and it does it.
2. Being able to be creative within bounds in a way that allowed me to learn new cool things each day and build with those new bits of knowledge upon other bits, to great things that were entertaining.
Without some bounds, chaos and floundering reign. Electric slot racing was cool because a realistic (per ratio) speed was involved, but control was possible, and it was a simple control, variable power to the engine. Having to steer those cars without slots at that speed is beyond our abilities. This is the problem today, to me. There are so many options. There are no slots in the track. No Apple II. And, there are now so many prewritten solutions. You don't need to write a game to find what you were thinking of. There is little reason for the younger generation to develop anything on their own. My kids just play games. I know I couldn't get them to develop if I tried, though I tried once and failed. They'd rather be creative with markers and paper- and that's ok. But, it makes me miss my younger years on the first home computers; I can't give that to them; that era is gone, and I miss it.
But I think learning to code is important because it is what attracts creatives, and both creatives and engineers are needed in development.
You're guessing here (and you admit it), but I'm a very strong data point for the opposite. Anyone who knows me would tell you I'm creative (I started out, and still am a filmmaker and it's all I'd do if I could afford it).
I had thousand of hours of computer science before I wrote my first line of code, at age 20, and I didn't seriously get into coding until I was 24.
So no, I don't think coding and creativity have any link whatsoever. I find CS extremely creative and enjoyable, much more so than coding, which I consider to be "S" work in the Myers-Briggs taxonomy. When I want to be creative, I step back into CS mode.
There are two things that attracted me to programming:
1. Telling something else to do what you want, and it does it.
2. Being able to be creative within bounds in a way that allowed me to learn new cool things each day and build with those new bits of knowledge upon other bits, to great things that were entertaining.
Without some bounds, chaos and floundering reign. Electric slot racing was cool because a realistic (per ratio) speed was involved, but control was possible, and it was a simple control, variable power to the engine. Having to steer those cars without slots at that speed is beyond our abilities. This is the problem today, to me. There are so many options. There are no slots in the track. No Apple II. And, there are now so many prewritten solutions. You don't need to write a game to find what you were thinking of. There is little reason for the younger generation to develop anything on their own. My kids just play games. I know I couldn't get them to develop if I tried, though I tried once and failed. They'd rather be creative with markers and paper- and that's ok. But, it makes me miss my younger years on the first home computers; I can't give that to them; that era is gone, and I miss it.