When Making a Comprehensive Retrofit of your Code...

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?

Comments

Re:fp

[Anonymous Coward]

Girl, you make a nigga wanna fuck.

eat my

[Anonymous Coward]

balls

thanks in advance

Try INTERCAL

[Doppler00]

Rewrite the code in intercal to really impress people!
You're code base will go from over a meg to at least 10 times that, and as a bonus, no one will ever be able to understand it.

The Blind Leading the Blind

[Junks Jerzey]

"Do such and such because I read in an interview that..."

"There's this cool buzzword called refactoring that my professor mentioned and so you should..."

"[blah blah blah] object orientation [blah blah blah]"

"I saw a book about Extreme Programming at the bookstore and..."

first thing you should do

[Anonymous Coward]

is keep people from writing it in perl since its a slow crappy language.