I agree with you but I also believe there needs to be limits. I like Google's strategy of N approved languages.
From an operational perspective there's too much overhead to effectively running any language in a production environment.
From a maintenance perspective you want to have common skill sets between a large intersection of employees so you're not the only person doing bug fixes on a system.
Good points. I took over management of a software development group that had a four server commercial product that was dependent upon having developers knowledgeable in all of the following: Windows, Linux, MSSQL, PostgreSQL, MySQL, C++, C, Java, C#, PHP, Perl, Bash, and Javascript.
The development team was very siloed. Nobody could work on anyone else's code, not even a little bit.
When a new developer approached me with a module that he had written in Jython, I almost lost it.
Comments
I agree with you but I also believe there needs to be limits. I like Google's strategy of N approved languages.
From an operational perspective there's too much overhead to effectively running any language in a production environment.
From a maintenance perspective you want to have common skill sets between a large intersection of employees so you're not the only person doing bug fixes on a system.
There needs to be a balance for sure.
Good points. I took over management of a software development group that had a four server commercial product that was dependent upon having developers knowledgeable in all of the following: Windows, Linux, MSSQL, PostgreSQL, MySQL, C++, C, Java, C#, PHP, Perl, Bash, and Javascript.
The development team was very siloed. Nobody could work on anyone else's code, not even a little bit.
When a new developer approached me with a module that he had written in Jython, I almost lost it.