in reply to Maintenance vs. Programming style

In the $work context, we have a standard .perltidyrc file that each programmer uses. Each person is free to program in whatever way they wish, but before checking in they should run the project through Perl::Tidy.

"Go up to the next female stranger you see and tell her that her "body is a wonderland."
My hypothesis is that she’ll be too busy laughing at you to even bother slapping you.
" (src)

Replies are listed 'Best First'.
Re^2: Maintenance vs. Programming style
by adamk (Chaplain) on Jan 28, 2008 at 23:00 UTC
    Unfortunately, on our current project, 90% of the "blame" in svn annotations for who wrote code is placed on the person who imposed Perl::Tidy on the (100-200k SLOC) existing codebase.

    Also, I don't trust Perl::Tidy to not break code.
      You of course sent examples to the author of Perl::Tidy? The same author who specifically says that it doesn't work for everything? Also the same author who asks for help in running down the problems found in the field-- Or is enough for you to say that you just 'don't trust Perl::Tidy to not break code'... Of course it might be the case that code that breaks Perl::Tidy is complex to the point that it needs to refactored anyway---hmmm, useful even when it doesn't work; hard to beat that!


      "Never try to teach a pig to wastes your time and it annoys the pig."