My problem is:
a) this assumes that people can not have ideas without a programming languages. That's obviously incorrect. I can have ideas without knowing a programming language.
b) languages also constrain the thinking. For instance, in ruby you have a class and a module, as distinction. Is that a useful distinction? I think it is overlapping, with modules giving more flexibility. In practice, this distinction does not lead to many problems, but if you have: class Foo; module Bar; end; end and then you were to write "class Foo::Bar" in another file because you want to modify the code quickly, then ruby says you'd have to use "module Foo::Bar" instead, because the ruby parser already knew that this is a module, not a class. It is not a big problem, but whenever I run into this issue, I wonder why I need to care whether it is a class, or a module. Because, when I do so, such as adding a new method to that, perhaps from another namespace/project, then I wonder why ruby does not prioritize me wanting to change the code, but instead complains about that it is a module or a class. (I understand the ruby parser has to work that way, in order to differentiate between errors made or mixing up code, but my point of contention here is the "class versus module" distinction. The above is one example of many more that can be found in programming languages.
Of course you can reason that better programming languages typically lead to better implementations too. I'd reason in favour of such a statement. I don't really see the point of learning a language that is inferior to languages I already know, when I know I am not going to use that language. The "learn a new language every year" is not a bad idea, but why would I want to learn languages that are bad? That makes no sense. There is competition between languages, as well as against time.
Which is precisely why trying out languages built on different paradigms is a good way to widen the way you think about programming.