Beefy Boxes and Bandwidth Generously Provided by pair Networks
There's more than one way to do things

comment on

( [id://3333] : superdoc . print w/replies, xml ) Need Help??
I think we should ignore the man-hour calculations which are a bit of an eye-roller.

Really? And why should that be? Let's take a look at the hours I've spent on Excel::Template.

  • I wrote E::T as a fork of PDF::Template, which I had taken over from Dave Ferrance. I would estimate he had spent between 100 and 250 hours on the 0.05 version. My initial release took 4 weeks to test, which is 160 hours, plus about 40 hours of design help and testing from a coworker. (200-450 hours)
  • The actual forking of E::T took about 4 days, resulting in an initial release cost of 30 hours. (230-480 hours)
  • I've released 24 updates to E::T. The minimum amount of work to release an update to a CPAN module is 2 hours. I generally put in about 5-20 hours per release, averaging about 10 hours per release. So, that's 12 hours per release, on average. So, 24 * 12 is 288 hours. (518-768 hours)
So, let's call it 600 hours of work put into Excel::Template. At a measly $25/hr (which is what sloccount appears to use), that's $15,000. For one distribution. CPAN has over 7000 distros. If we assume E::T has an low-to-average cost (which I would say is about fair, given the Acme namespace vs. DBI or CGI), then that's a minimum of $105 million dollars. Hmm ...

My criteria for good software:
  1. Does it work?
  2. Can someone else come in, make a change, and be reasonably certain no bugs were introduced?

In reply to Re: Size of CPAN by dragonchild
in thread Size of CPAN by tomazos

Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":

  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.