All the Perl that's Practical to Extract and Report
use Perl Log In
jonasbn (1153)
reversethis-{gro.napc} {ta} {nbsanoj}
http://e-diot.dk/
AOL IM: BJonasN (Add Buddy, Send Message)
Perl Programmer located in Copenhagen, Denmark. Active member of Copenhagen Perl Mongers.
Author of:
- Business::DK::CPR
- Business::DK::CVR
- Business::DK::PO
- Business::OnlinePayment::CashCow
- Date::Holidays
- Date::Holidays::Abstract
- Date::Holidays::Super
- Date::Pregnancy
- Games::Bingo
- Games::Bingo::Bot
- Games::Bingo::Print
- Module::Info::File
- Module::Template::Setup
- Test::Timer
and maintainer of:
- Tie::Tools
- XML::Conf
- Workflow
Workload vs. Workflow
My workload has increased seriously. Most of the time I spend in front of the computer seems to be work related. Meaning billable hours, working on code related to or owned by clients.
This is of course good, but...
I does make me feel that I am disregarding my open source/freeware work, such as my CPAN modules.
I was so lucky that some of the work was directly on an open sourced module. Anyway a few nights ago I however got some work done on the Workflow module.
- I accepted and adapted a received a patch (thanks Jim)
- I implemented some tests, raising the test coverage with a few percent
- I added some more POD, addressing POD coverage
It really felt good, eventhough it was peanuts.
My overall plan is to get as high test coverage as possible. When this is done I will analyse the code with Perl::Critic using relevant policies.
Based on this output I expect to refactor the code heavily, using the unit-tests to ensure nothing it broken. With the current coverage of about 68-69% we are still not at a level where I find it safe to do so, but we are slowly getting there.
The final product of the refactoring should perhaps be released 1.0.0.
Man, that would be good
--Larry Wall in stab.c from the perl source code
Workload vs. Workflow 0 Comments More | Login | Reply /