Scenario 2: Clearly the child that did the research did a better job, since the objective of education is the acquisition of knowledge, including the recursive knowledge of how to go about finding the stuff that you want to learn about (Google, the library).

Scenario 1: A little tougher. Strictly on a code basis, I would favour the first programmer, even it burns me to hear (as it has other respondents here) that someone spent a weekend working up a demo instead of spending time with their friends or family. (Side note: I sure hope the manager who requested the demo on short notice gave Programmer A some time off in lieu. Sometimes business provides opportunities with short time-lines -- that's the way it is, folks.)

On a knowledge basis (that means, could the progarmmer answer a knowledge-based question in a demo), Programmer A is way ahead, having studied the manuals in question and having written code from scratch. I don't think anyone could argue that they would know code that they'd downloaded and studied better than code they'd written themselves.

Again, this is another "It depends" situation, since it could be that a large piece of the demo is covered by a mature CPAN module, and a wrapper is all that's needed.

--t. alex

"Mud, mud, glorious mud. Nothing quite like it for cooling the blood!" --Michael Flanders and Donald Swann

In reply to Re: Initiative or otherwise? by talexb
in thread Initiative or otherwise? by BrowserUk

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.