Your choice of metaphors is apt. As I have all-too-often said:,
Give a man a fish, and he'll eat for a day;
Teach a man to fish, and he'll spend his life savings on fishing tackle.
This is not necessarily a bad thing -- the Perlish equivalent might be:
Give a man a snippet, and his program will run for a day;
Teach a man to use PM, and he'll never get back to that code he was supposed to write.
Seriously, though, I think that the need for Socratic learning is related to the kind of question being asked. A general "what method do I use" question needs multiple answers, per TMTOWTDI. But a specific "why is this code fragment broken" question probably deserves a more direct answer.
Determining whether or not I actually provide direct responses when I should do so is left as an exercise to the reader.
-
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.
|