I would like to adopt a uniformed way of writing in house scripts and
tools between the different admins, its been a uphill battle trying to
get everyone to confirm to one particular language this is becoming a
bigger problem as our staff expands.

Right now its a big toss up between Perl and Python and few who insist
on using ksh/bash for everything I had no idea you could write socket
code with bash till I seen calls to /dev/tcp in a bash script lol.

As the lead engineer i'm almost ready to make it mandatory for
everyone to learn and use python as unlike perl and other scripting
languages it forces strict style formality and with its vast array of
objects/types and built in routines you can clearly identify what the
code is doing, no time spent reinventing the wheel or spending time
trying to read complex regex.

I dont want this to end up in a Perl vs Python vs XYZ but I am open to
friendly discussings about why this is good and bad. We are in the
financial service industry and Perl is the natural choice for most
firms.

How are others handling situations like these?

--
Rodrick R. Brown
Senior Systems Engineer
http://www.rodrickbrown.com
http://groups.yahoo.com/group/wallstandtech