comment on

I definitely agree.

I have to caution that we do not have enough information to make an informed call on the skills of programmer B - neither as far as his abilities as a programmer are concerned nor about his ability to judge the quality of the downloaded code. Nor do we know how critical the task was and how acceptable a sloppily coded solution might be in this case.

But I feel that in practice, people who take this approach are cargo cultists far, far more often than not.

Not reinventing wheels is a good mindset, but it requires being able to tell round wheels apart from square ones. Many people quite simply lack the experience and expertise to do so. That is why places like the CPAN are so important.

Generally, scenario one is much harder to judge than scenario two, irrespective of the fact which has already been pointed out that the goals differ.

Makeshifts last the longest.

In reply to Re^3: Initiative or otherwise? by Aristotle
in thread Initiative or otherwise? by BrowserUk

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.


more useful options
	PerlMonks