I started perl because of extending nagios in the 200X years.<p>Then I started to write fast hacks with it (iptables to excel, monitoring to Jira, parsers, cron's, etc) really useful for daily needs at $job.<p>Then I started to write web dashboards (Catalyst and first Dancer releases, ok the first one was CGI) with EXTjs and jquery frontends. My team mates did find those dashboards useful.<p>Last years I've work with AWS and other APIs (i.e. vmware apis), doing more modern web applications using perl (and twitter bootstrap, JSON web tokens, Oauth, swagger, etc) and it did the job.<p>My hobby project is a lottery predictor using perl, sometimes I get more refunds than when I did use random numbers... still not rich :-)<p>Usually, the language is not the barrier (if it provides standard basic needs, like web frameworks, library bindings and ORMs). The programmer is the barrier.<p>If you can glue SSH, State, Metrics, DataWareHouse, and HTTP (API and frontend) you can do devops.<p>This talks about devops and perl, so now I would like to point to Paws!<p><a href="https://github.com/pplu/aws-sdk-perl#trying-it-out" rel="nofollow">https://github.com/pplu/aws-sdk-perl#trying-it-out</a><p><a href="https://aws.amazon.com/blogs/developer/hello-perl-developers/" rel="nofollow">https://aws.amazon.com/blogs/developer/hello-perl-developers...</a><p>I can say that at least one person (me) has been successful, bridging operations and developers teams, using perl, until the present.<p>You just need a couple of frontend and API design skills, and then people doesn't care about your backend, while your service is useful.<p>Articles about this, always mention TIOBE... I never did care about it, I just put my effort in getting my job done. I care more about teammates congratulations.