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 ]

dws (341)

dws
  (email not shown publicly)
http://www.davewsmith.com/

Journal of dws (341)

Tuesday September 23, 2003
11:57 AM

Never buy a car built on a Monday

[ #14859 ]
When I was growing up, the family business was a Ford dealership. One of the bits of unwritten wisdom then was to never buy a car that was built on a Monday (or during labor negotiations), as they tended to suffer from more problems than cars built mid-week. (The image was of hung-over factory workers returning to work after weekend-long benders, picking up tools and then trying to assemble your car.)

I'm wondering if there's a similar effect with code. That is, do defects tend to correlate with the day of the week (or the day into the project) when code was written? I'll bet there are some interesting patterns there, should someone care to do the legwork. I've taken it as far as musing about whether there's enough information gleanable from CVS to timestamp each row of a file. At that point, this joined the list of "neat projects that'll never get off the ground in this lifetime."

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.
  • I definitely have days when I know code won't be written. So I try not to write it on these days.

    Or is it just progressive slacking ? hmm...

  • RT Stats (Score:3, Interesting)

    by Matts (1087) on 2003.09.23 13:46 (#24447) Journal
    I was playing with the RT statistics tools today. The only graph of interest to our projects (*) was the "when do bugs get filed/resolved" graph. This showed that most bugs got filed on a friday, but most bugs got fixed on a Tue/Wed/Thu.

    Interesting.

    (*) I think the package was mostly intended for call centres using it as a tracking tool.
    • The bugfixes all introduced faults that were discovered on Friday. :P ;)

      Unless, of course, you're properly testing your code and not releasing unless all tests pass. :)

      --
      J. David works really hard, has a passion for writing good software, and knows many of the world's best Perl programmers