CPAN for Work & Lightening Talks

Provides 'grokkable' chunks of usable code. Forces thinking in terms of modularity and distributable structure.

Forms a best practice, even if not released to CPAN.

Refactoring forces chunking of code to best purpose units (for example, one line subs (Ingy)

People complain that refactoring is time consuming, unrewarding, repetitive.   These are barriers to entry into CPAN authoring.

Using the CPAN tools, module developing is more effective.

SocialText story

    Ingy.  Selling Wiki's to F500.  small staff, strict budget.
    
    Use XP across the board and refactoring.  Driven by customer drive.
    
    Code was initially a single CGI, now split into 150 pm.  Based in Kwiki in an OO hierarchy. [is there a purple plugin for kwiki?]
    
    Danger of code duplication.  Having removed it, modules can be very specific without overlap, so code is simpler to write (with no impact to other bits).
    
    Use of Spork - inherited from kwiki.

OurInternet

    Shell company, no overhead.  FUnctions as a shim between clients and developers.  Most work ends up in CPAN mods
    Code -> CPAN
    Various projects.  Using PDF modules.