Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have a very cluttered code, and the current revision is almost complete, meaning all functionalities i wanted for this revision/sprint are done.
Should i finish this revision as it is and refactor it later or should i refactor it right now?
There is no “correct” answer for this, it’s really a matter of priorities?
You have to consider all of these questions together. I typically find that refactoring can, especially on larger projects be much more time and effort then you think it may be. You may also be breaking things (this is where unit tests are amazingly helpful).
I typically will strive for release on commercial projects then refactor unless there’s major problems with the existing code.