in reply to Re: Writing general code: real world example - and doubts!
in thread Writing general code: real world example - and doubts!

Not only your suggestion seems reasonable (Keep It Simple, Stupid is illuminating on the top of my current PerlMonks page!), but it also seems a good practice given all the answers below. I would also thank you for your practical advices - I'll try to solve problems in the most straightforward way, avoiding evident and immediate in-flexibilities and trying to remain flexible myself to future changes.

About refactoring, I maybe missed the correct word - as a matter of fact, I was trying to pre-refactor just to be sure not to have to do later. I had to wait the moment in which this would have been really necessary!

Flavio (perl -e "print(scalar(reverse('ti.xittelop@oivalf')))")

Don't fool yourself.
  • Comment on Re^2: Writing general code: real world example - and doubts!

Replies are listed 'Best First'.
Re^3: Writing general code: real world example - and doubts!
by adrianh (Chancellor) on Apr 06, 2005 at 09:29 UTC
    I had to wait the moment in which this would have been really necessary!

    I think that's the key point to take away. The whole idea of refactoring is to make your code simpler. If your code is getting more complicated to understand something is probably going wrong :-)

    The time to refactor is when the code let's you know that refactoring is necessary (through duplication, hard to understand code, etc.)