What you have seems to me to be mostly a management problem. If the management can't set up and enforce code guidelines, all your efforts will be in vain.
If you think that there are modules that should be used, make the case that they should be used within the programming guidelines.
Your perceived lack of concern for DRY might well be you overarchitecting things and trying to eliminate perceived repetition where the similiarity is just in the code but not in the business that originated the code to be written.
Such code can be used to give any language a bad reputation, but the problem is not the language but the programmers, and the management that lets those programmers be. My recommendation is to either find an angle with management to improve the programmers, or to adjust your stance on things so you can live with the situation or to leave.
In reply to Re: poor quality perl code
by Corion
in thread poor quality perl code
by pwagyi
For: | Use: | ||
& | & | ||
< | < | ||
> | > | ||
[ | [ | ||
] | ] |