in reply to Advice on best practices

If you are both “consultants working for the same company,” and therefore you are not the person for whom this consultant is working and/or someone whose ability to do your job is not directly and materially affected, then I would cordially suggest that you ... well ... “mind your own business.”

Although the methods being used by this person might “smell bad” to your own personal set of sensibilities, you don’t know what instructions this person might have been given by the person who issued his contract, and you also don’t know what is or isn’t important from the point of view of the person who is signing his checks.   None of the decisions he’s made are indefensible.

It’s not only bad form for one consultant to question another consultant’s methods or competence ... it can well be political therefore career suicide.   If he does anything at all with Perl, he knows about PerlMonks, and it won’t take him long to find out that he’s been pretty well body-slammed there.   Not the wisest move you’ve ever made ...

Replies are listed 'Best First'.
Re^2: Advice on best practices
by Anonymous Monk on Mar 05, 2015 at 23:18 UTC
    mind your own business

    sundialsvc4, on your home node you advertise your services as "... spends most of his professional time with legacy software projects (in Perl and otherwise) that have wandered far off-course, playing a pivotal role in turning the projects around and restoring the software to reliable service". Advising goldcougar to leave potentially bad code unquestioned could be advantageous to your business. That's not just a conflict of interest, that's somewhere in the gray area of criminal business practice.

    Then again, you're probably just trolling for Worst Nodes as usual.