In general I'd agree with you, except that it takes more time to write down the approach to the solution clearly than to provide the code. This may seem at odds with intuition, but I guess more experienced programmers/problem solvers than myself will agree.

There's another point to consider: often a solution to a problem comes as a "flash of inspiration" rather than a consicious process. In such cases I don't know how to explain the path to the solution, it just appears before the mind's eye.

But yes, you certainly have a very valid point and maybe we should make the effort to emphasize problem solving approaches rather than provide just a piece of code that works (or should work ;-)
I'll try...

Just my 2 cents, -gjb-

In reply to Re: Solution Approach by gjb
in thread Solution Approach by artist

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.