From the sound of things, you did exactly what she asked for.
- You didn't belittle her for not knowing what you know.
- You didn't suggest a solution that involve changing the inputs to the problem, or changing the problem to suit a solution you knew.
- You didn't preach to her about CPAN, or POD, or perldoc, or Supersearch.
- You didn't berate her coding style, variable names, tab settings or editor choices.
- You didn't assume that because you didn't understand her problem, that she was tackling the wrong one.
You gave a working solution to her immediate problem, that along the way, demonstrated the power of the 'use CPAN' mantra,
... without going all PerlMonks on her.
And you have left her to learn the lessons of your demonstration, in her own time and her own way. Nice one++.
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
-
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.
|
