Jump to content

  • Log In with Google      Sign In   
  • Create Account


#ActualOlof Hedman

Posted 24 September 2012 - 04:30 AM

I have found that the "quick and dirty way" is an illusion, and isn't really quick at all, it just means you put off work until later, and produce less useful code with more bugs that haunt you later.
Sure, for some prototyping it can be motivated, but it should be cleaned up before commit to the trunk.
For longer prototyping, a branch might be motivated.

That doesn't have to mean you have to do a _refactor_ every time, if your design is sensible to begin with, it shouldn't be very hard to add functionality in a graceful manner, no matter what this functionality might be.

Though, of course your design is never perfect, and sometimes needs a slight refactor.
As others have pointed out, these should be done on a stable code base, so you can verify it works as it should both before and after.

#1Olof Hedman

Posted 24 September 2012 - 04:29 AM

I have found that the "quick and dirty way" is an illusion, and isn't really quick at all, it just means you put off work until later, and produce less useful code.
Sure, for some prototyping it can be motivated, but it should be cleaned up before commit to the trunk.
For longer prototyping, a branch might be motivated.

That doesn't have to mean you have to do a _refactor_ every time, if your design is sensible to begin with, it shouldn't be very hard to add functionality in a graceful manner, no matter what this functionality might be.

Though, of course your design is never perfect, and sometimes needs a slight refactor.
As others have pointed out, these should be done on a stable code base, so you can verify it works as it should both before and after.

PARTNERS