Beefy Boxes and Bandwidth Generously Provided by pair Networks
Just another Perl shrine
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??
I disagree that, as a consultant, one's role is to simply shut up and do as you're told. I take the view that I am being hired for my expertise and to just keep my opinions to myself rather than freely offering that expertise would be a disservice.

When my clients request that I do something I disagree with (or something I simply don't want to do), I lay out my reasons, ask about why they want to do what they asked in the way they specified, and try to explain why my way would be the better option. It's also important to make it very clear to them that you'll gladly do it their way if that's still what they want after reviewing your arguments1, of course. My clients respect this and I have the distinct impression that it is one of the major reasons why my repeat customers keep coming back.

1 Provided that's true. One case that comes to mind is someone who wanted an application created which not only violated a third-party website's ToS, but also had a large degree of complexity specced which was clearly intended solely to bypass that site's attempts to enforce their ToS. When they displayed a lack of interest in looking for ways to obtain their data in a ToS-compliant manner, I said "I'm not comfortable with doing this project" and walked away.


In reply to Re^2: How to retain perl in-house code by dsheroh
in thread How to retain perl in-house code by basicdez

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others browsing the Monastery: (4)
As of 2024-04-19 13:29 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found