This is a problem with your co-workers and the environment.

Your developers are well known (in Scotland at least) as jobs-worth, i.e. 'that's more than my jobs worth'. Aka unprofessional, selfish gits.

First step - take a break. The people here aren't your enemy. Neither are your co-workers. Neither is perl. Kick a ball around to blow off some team, go for a run - SOMETHING!!!

Second step - gather some examples and evidence of bad code. Gather some examples of good coding standards from successful perl using companies. Go to your management and make your case:

• Our perl scripts need mucho maintenance because they are not modularised
• We are constantly reinventing the wheel - this is costing us money with no good reason
• Our scripts are not robust
• We have an adverserial culture where no one is prepared to take responsibility. We're supposed to be working as a team but because we aren't, we're spending more time infighting than fixing problems

You can't change your fellow coders if they don't want to change. You can change management if you make a reasoned case showing clear, tangible £££ savings. They may even thank you.

Your co-workers won't but maybe they will find new jobs.

Good luck, I've been in the same boat and it really sucks.