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?
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
Do 'Extreme Programming' principles dictate that I get an afro perm and adorn my body with piercings and generic "tribal" tattoos? I can't even spell snowboard. Oh my...
Do 'Extreme Programming' principles dictate that I get an afro perm and adorn my body with piercings and generic "tribal" tattoos?
First time I heard the term, I asked the guy "Is that where you jump out of an airplane with a parachute and a laptop?"
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.
Indead. I'd like to extend this advice:
--
Ilya Martynov (http://martynov.org/)
My favorite comment to see in the code "This is a bit of a hack"