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.

use Perl

All the Perl that's Practical to Extract and Report

I Cringe More | Login | Reply

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Without JavaScript enabled, you might want to use the classic discussion system instead. If you login, you can remember this preference.

Possibly Partly Correct (Score:3, Insightful)

by chromatic (983)

I saw that earlier today and sent Cringely a lengthy e-mail. Here's the conclusion:

Now rewriting code for the sake of rewriting (without a concrete goal in mind) or refactoring without tests are both silly and oughtn't be done and happen all too often in the open source world. They also happen in the proprietary software world too, unfortunately.
We just hear about them more in the open source world; there's less to hide.
Good on you for suggesting a free day pass to Testing Boot Camp, though.
- Re:Possibly Partly Correct (Score:1)
  
  by kjones4 (3231) <kellymjones@gmail.com> on 2003.05.04 3:42 (#19765) Journal
  
  *Any* time I've cleaned up code, it's been to fix known problems. Maybe I have a different definition of cleaning up.
  
  Reply to This
  
  Parent
  - Re:Possibly Partly Correct (Score:2)
    
    by pudge (1)
    
    And one of those problems is often that IT IS UNMAINTAINABLE as-is, and NEEDS TO BE MAINTAINED. "This car works, despite the duct tape on the hoses ... if I replace the hoses, gosh darnit, the car might stop working!"

Get More Comments

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.