Well... Perl is in my primary job description and I know for certain (I sit next to a Java programmer) that I don't code as much as other programmers.

Maybe it is because you don't have to code as much in Perl because of the exquisitely tastey documention, a massive pile of freely distributed modules, and the elegance of an expressive syntax.

I find that most times, with other languages, I spend plenty of time fighting with undocumented "features" in the syntax, undocumented "features" in libraries that cost $$$$, writing a library that should exist but doesn't, or writing a library that costs more $$$$ than we have to spend. With perl, once I reached a certain level of proficiency, writing the code was only slightly slower than thinking. Which leaves me plenty of time to read even more of that yummy documentation, and plan for my projects better :P

Also, I've learned that working too fast gets you in trouble. Best to take your time and do it right the first time. That way people don't expect fast answers and the answers you give always look good ;)

I pray the winds of power where I work never change, Perl is just the niftiest toolbox I've had to date and it suits me JUST FINE.