Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

SQL-Ledger 2 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.

  • While I am impressed with its list of features, I am less than impressed with its quality. I did an internal review of this product for where I work and I found a few problems [perlmonks.org]. Unfortunately, I was taken to task for this [geocrawler.com] and the lead developer referred to my concerns as being "nonsense". That was interesting because I merely listed my conclusions, but not how I arrived at them.

    I would love to see SQL Ledger be turned into a good, solid product that I'm not afraid to touch. (psst ... maybe you want to

    • Yea, I read all of that when I got home from the meeting where I said "I believe a safe estimate for adding your changes would be about four days." Maybe this will finally teach me to research thoroughly a package before I try to make estimates on it.

      On the one hand, I should have read this before my meeting and been prepared to give a more accurate estimate. On the other hand, learning this package and getting the functionality they want by Monday is proving to be a fun challenge that I am enjoying more and more.

      And to answer your question, yes. I'm going to definitely start that before I edit anything aside from the aesthetics.
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.