This was another one of those blog posts that started with <insert inflammatory title about X being bad/dangerous/perilous>, followed by <poorly constructed straw man about X being done wrong in a way that rarely happens> followed by <largely obvious but still unsupported conclusion that X is actually really good but only when done right>.
The empty argument sandwich.
Polyglot programming is not about using 10 languages in every (or any) software project. It isn't even necessarily using 3. The one statement made that was true was this:
> 2. Knowing multiple programming paradigm expands your mind and makes you better at programming in every language.
Which he then argued against with
> Well, maybe the second I'll argue with a little: I think you can get most of the benefits by using different paradigms within the same multi-paradigm language
Ironically, "#2" actually supports the counter-argument. Learning multiple languages would be extremely useful when then applying those paradigms within a multi-paradigm language (as an example playing with Erlang and F# has made me better with languages that support first-class functions like C#, Ruby and Javascript).
In the end, the article seems to disagree with it's own title. There is no peril to being a polyglot programmer. There is perhaps a peril in overuse and over mixing of tools, which we should all know and has nothing to do with being a polyglot programmer. Perhaps a better title would have been the perils of indecisiveness, or having a lack of focus, or doing too much at once. I dunno.
The empty argument sandwich.
Polyglot programming is not about using 10 languages in every (or any) software project. It isn't even necessarily using 3. The one statement made that was true was this:
> 2. Knowing multiple programming paradigm expands your mind and makes you better at programming in every language.
Which he then argued against with
> Well, maybe the second I'll argue with a little: I think you can get most of the benefits by using different paradigms within the same multi-paradigm language
Ironically, "#2" actually supports the counter-argument. Learning multiple languages would be extremely useful when then applying those paradigms within a multi-paradigm language (as an example playing with Erlang and F# has made me better with languages that support first-class functions like C#, Ruby and Javascript).
In the end, the article seems to disagree with it's own title. There is no peril to being a polyglot programmer. There is perhaps a peril in overuse and over mixing of tools, which we should all know and has nothing to do with being a polyglot programmer. Perhaps a better title would have been the perils of indecisiveness, or having a lack of focus, or doing too much at once. I dunno.