Not all people who have to program in Perl are programmers. And in many organizations it would be irresponsible to insist that they should be.

It is often wise to give some measure of responsibility to your users. They have jobs to do, and it would be unwise for you to make your professional programmers a perpetual bottleneck for all aspects of that process. Should you be involved for some activities? Yes. But just as you do not need an architect to put a picture up in someone's home, you should not need a programmer to modify a personal utility script.

However when you do that, you now have people who are not programmers who need to program. Should you insist on making them all programmers? I think not!

This is one of the prime reasons why Larry Wall insists that baby Perl is Officially OK...