Slashdot Mirror

← Back to Stories (view on slashdot.org)

When Making a Comprehensive Retrofit of your Code...

Posted by Cliff on from the things-you-do-when-you-rewrite-everything dept.

chizor asks: "My programming team is considering making some sweeping changes to our code base (150+ perl CGIs, over a meg of code) in the interest of consistency and reducing redundancy. We're going to have to make some hard decisions about code style. What suggestions might readers have about tackling a large-scale retrofit?" Once the decision has been made for a sweeping rewrite of a project, what can you do to make sure things go smoothly and you don't run into any development snags...especially as things progress in the development cycle?

2 of 385 comments (clear)

  1. Listen To The Experts by ChuckPollock · · Score: 3, Funny

    The First Rule of Program Optimization: Don't do it. The Second Rule of Program Optimization (for experts only!): Don't do it yet. -- Michael Jackson

  2. Re:Sleeping dogs by bbqdeath · · Score: 5, Funny

    I second the concern about PERL. And I offer my advice as someone who has virtually no qualifications to talk about large systems of code. I just like Python better than PERL because it doesn't hurt my eyeballs like PERL.

    Yeah, I guess this is a troll. But it's honest. I use Python like most people use toilet paper: several times a day, and for more things than it was originally intended.