I agree - it will probably be best to accept the project just as any other shrink wrapped system we buy.
I is a terrible shame though that all the effort that has gone into this project has ended with such a poor result. If it had been done according to 'proper' software engineering methods, it could have been augmented with you referrer-scanning logic and my additions.
It does make the program less useful because you and I have had to do something else, and thus we have had to spread our tuits. The program could have saved us valuable time for something vital (like playing with the dogs) instead of having to do something that has beeen done many times already. If the implementation is 'nice' (from an engineering point of view) it adds considerable value. OK: it does as advertised, but extra value can be had if it is possible to reuse parts of it in new and unforseen ways. I think that perl (and Perl) is a good example of this.
-
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.
|
