Re^2: Is there any way to shut off deprecated, dangerous, dilapidated, or otherwise undesirable language features?

Thanks very much, Dave.

The situation I'm thinking of is when you've got a handful of people working on a given project, with questionable or little leadership, where one or more of the team are hot-doggers who like to bang out a major feature overnight leaving behind some dodgy ("but it works!!") code that everyone else now has to document and maintain.

For this situation, it sounds like using Test::Perl::Critic on the dev server (and requiring that all code use warnings FATAL all) might be the way to go. As long as you can get everyone to agree on it beforehand.

Comment on Re^2: Is there any way to shut off deprecated, dangerous, dilapidated, or otherwise undesirable language features?

Replies are listed 'Best First'.
Re^3: Is there any way to shut off deprecated, dangerous, dilapidated, or otherwise undesirable language features? by locked_user sundialsvc4 (Abbot) on Aug 14, 2012 at 17:19 UTC
Then, the question becomes whether or not you are in a position of authority over them. If they do not have leadership now, perhaps you can become the leader so as to knock a little sense into them. Otherwise, and I kid you not, sometimes the right thing to do is to start forwarding Monster job-offers anonymously into their in-box. When someone like that sees greener grass, he or she will reliably jump ship. (“Hot doggers” are especially reliable, because they always think that they are God’s Gift to everything, and that none of the mortals around here appreciate their Brilliance.) A slightly craftier approach is to do that to the current project manager, if you think that you can then be internally promoted. `:-D` Failing that, you jump ship. Because, if the company’s management practices are to allow junk-code to proliferate and they will not exert proper project-management control, you don’t want to be left maintaining that or dealing with that. This is how “death marches” happen. If you can positively change the situation, do so. If not, escape it.

Replies are listed 'Best First'.

Re^3: Is there any way to shut off deprecated, dangerous, dilapidated, or otherwise undesirable language features?
by locked_user sundialsvc4 (Abbot) on Aug 14, 2012 at 17:19 UTC

Then, the question becomes whether or not you are in a position of authority over them. If they do not have leadership now, perhaps you can become the leader so as to knock a little sense into them. Otherwise, and I kid you not, sometimes the right thing to do is to start forwarding Monster job-offers anonymously into their in-box. When someone like that sees greener grass, he or she will reliably jump ship. (“Hot doggers” are especially reliable, because they always think that they are God’s Gift to everything, and that none of the mortals around here appreciate their Brilliance.)

A slightly craftier approach is to do that to the current project manager, if you think that you can then be internally promoted. :-D

Failing that, you jump ship. Because, if the company’s management practices are to allow junk-code to proliferate and they will not exert proper project-management control, you don’t want to be left maintaining that or dealing with that. This is how “death marches” happen. If you can positively change the situation, do so. If not, escape it.