I am a computer scientist, and even though I've used python extensively in both product development as in prototyping,
and I honestly don't think python helps people here.
If you want people to learn to think as a computer scientist via programming languages, teach them at least 1 language in the 3 major paradigms (OO, FP, declarative).
(There's more to learn: data structures, architecture, math, .... that I will not delve into here...)
The problem is that the insight comes at a price: You'll start comparing and might conclude that LanguageX is not suited for taskY.
Python isn't suitable for everything, but very often it's good for at least a prototype.
Well, yes, but you're missing the parent post's point. It's not saying that python is a bad language, that's sorta irreverent. The post uses understanding a language decision itself as an example of "thinking like a computer scientist." No matter how good or bad any single language is, learning to use language is not "thinking like a computer scientist."
OK, I agree. In the computer science sense, I enjoy Python because I find it has a high degree of transparency. That is just a personal judgement though.
If you want people to learn to think as a computer scientist via programming languages, teach them at least 1 language in the 3 major paradigms (OO, FP, declarative).
(There's more to learn: data structures, architecture, math, .... that I will not delve into here...)
The problem is that the insight comes at a price: You'll start comparing and might conclude that LanguageX is not suited for taskY.