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’ve got an application that just shipped. Since I wrote it, I’ve learned about amfphp and propel. Both would be ‘nice’ to be used in the application but I can’t say that it would be required at this point.
What types of things do you consider before you refactor code?
Should I?
Just be cause I can refactor the code does not mean that I should refactor the code. In many, many cases, there are far more important things that need to be done. Like fixing defects.
Now, if we’re talking about refactoring the code because I am already in that particular block of code and working on it as a part of defect resolution or code maintenance, that’s a different story altogether. But refactoring just for the sake of refactoring? That sounds like busywork born out of boredom. Surely you don’t have an empty defect list.