comment on

The part of this story that strikes me as sadly negligent/incompetent is that the designer or manager either didn't bother creating a (good) proof of concept or prototype for what was clearly a fairly radical idea.

Experimenting is a good and positive thing, but only the silliest developer/manager would put experimental ideas into production w/o testing them first, or at least making sure that that more conventional alternatives could be quickly put in place.

Reuse is a good thing, too. Reuse of code via the use of proven APIs, CPAN modules, libraries, etc. is a truly wonderful thing. Stupid/forced/kludgy reuse (remisuse?) is inefficient at its best, and pernicious at its worst.

Hanlon's Razor - "Never attribute to malice that which can be adequately explained by stupidity"

In reply to Re: The crime under reusability by Art_XIV
in thread The crime under reusability by pg

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