comment on

Hmmmm ... I think public ridicule and humiliation are your best bet. I would suggest setting up a fake blog that describes a similar situation (make sure you date it for about two or three years ago). Seed it with a bunch of comments that don't specifically answer the red-herring question of security but answers that ridicule the question. Once you have that up and running, submit it to digg or reddit and have your friends and coworkers upvote it. Once it's on the front page, just casually mention to manager and manager^2 what you've found during your *research*. Hopefully that will flow up (or down) and manager^3 will see the question as pretty irrelevant.

Okay ... it's either that or just tell manager^3 you think his question is silly -- you want a new job anyways.

-derby

Update: Just humor people ... I think perrin's answer is probably the best so far.

In reply to Re: How to answer "Perl is not secure" objections? by derby
in thread How to answer "Perl is not secure" objections? by radiantmatrix

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.


P is for Practical
	PerlMonks