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.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Right-O (Score:3, Insightful)

    by wickline (135) on 2003.05.23 8:02 (#20455) Journal
    > Proof that every company's financial department
    > should have at least one Perl programmer.

    and so should every other department.

    I bet that if I were to sit behind a random employee for a day, I'd have very good odds of finding something they're doing that could be made more efficient with a perl script or few.

    If I didn't already have plenty of stuff to do at work, I'd actually like to do that sort of shoulder surfing. Too few folks know that we're available to make their lives easier. Of course, if more folks know, they'd have to hire more of us, but I think the gain in productivity would be well worth it.

    Every department everywhere needs a staff of roving perl programmers on the look out for tasks to simplify and automate :)

    -matt
    • Yes, but then you risk putting the guy who gets the specifications from the customer and brings them to the programmers out of work.</Office Space>

      It'd be an interesting freelance service, but then 90% of the demand would be on Wintendo and probably more tedium than fun.

  • You might also find Spreadsheet::ParseExcel [cpan.org] and Spreadsheet::ParseExcel::Simple [cpan.org] useful.

    John.
    --

  • You might want to peep through AnyData and DBD::AnyData sometime. :-)

    LOADS of fun can be had with these.
  • When I have to mess with CSV material, I almost always use Text::xSV and dump it into a SQLite database. DBD::SQLite is much more fully featured than DVD::CSV (IMNSHO), and I'm not above dropping out of perl to the db shell for a few statements to best determine where to focus my code.

    SQLite never fails to amaze me with the high degree of features and performance coupled with vastly easy use. Few "throw-away" projects would have me dump data into a "real" db, even one I have running on the system, but I