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

use Perl Log In

Log In

[ Create a new account ]

Ovid (2709)

Ovid
  (email not shown publicly)
http://publius-ovidius.livejournal.com/
AOL IM: ovidperl (Add Buddy, Send Message)

Stuff with the Perl Foundation. A couple of patches in the Perl core. A few CPAN modules. That about sums it up.

Journal of Ovid (2709)

Wednesday July 08, 2009
11:08 AM

Complexity Management

[ #39254 ]

For some reason, I tend to get hired to work on large code bases, even though I've met many people who seem to have those perfect memories and instant analytic abilities which make them a natural for said code. Ultimately, as your code grows, complexity management skills become extremely important. This is why I have a number of modules I've written or contributed to heavily in order to make this easier:

Test::Harness
Complexity mangement starts with tests
Class::Sniff
When your OO hierarchy becomes unwieldy, take a closer look at it.
Class::Trait
Traits (roles) usually provide better OO complexity management than inheritance. (I should deprecate this in favor or Moose::Role)
Devel::Deprecate
You're going to forget to remove that out-of-date feature. This module won't let you forget.
Test::Most and Test::Kit
Stop duplicating test boilerplate in your tests and just get your work done.

Seriously, folks. As you move through your programming career, start paying attention to complexity management. When something is overly complex, figure out how to automate or simplify it. You'll usually gain flexibility and comprehensibility. Complexity management is your real job.

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.