The amount of energy that I have to devote to perlmonks is highly variable, and therefore I wouldn't want my name listed as an official resource for an entire subject area. Also I suspect that mentoring works best when the mentor and mentee have an established relationship rather than switching with every subject area. (Mentoring in my eyes is distinct from teaching...)

Others may have similar concerns.

Additionally I don't think that popular voting by perlmonks people is a good way to establish expertise. For instance I am often thought to be good at "functional programming". In fact I happened to post some influential articles while integrating together my understanding of how to program using closures. Accidentally I did use some functional techniques, but that was an accident since I didn't know what functional programming was. Furthermore in making up a name for what I was doing I accidentally caused many Perl people to define functional programming somewhat differently than it is understood by the broader programming world.

My "expertise" would not, for instance, be sufficient to be of much assistance to someone who was trying to translate an example program from Haskell into Perl.

In reply to Re: A PerlMonks mentoring list by tilly
in thread A PerlMonks mentoring list by dragonchild

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


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • 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:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, 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, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.