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.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||