A big advantage of refactorization for the customer is the reduction of the cost of introducing new changes. This is one of the arguments that can actually convince them. Nothing convinces business as much as money :)
While time and money are synonymous I find that explaining that the change will make it faster for you to in mplement changes in the future can make business a bit more open to the idea of 'wasting' time with a refractor.
Yes and no. I want to refractor because the code base is terrible to try and understand. It takes far too long to walk through. A refractor will keep me from taking a week to understand the flow which will save money. Personally I'm more concerned by the headache of trying to follow the code flow.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
A big advantage of refactorization for the customer is the reduction of the cost of introducing new changes. This is one of the arguments that can actually convince them. Nothing convinces business as much as money :)
While time and money are synonymous I find that explaining that the change will make it faster for you to in mplement changes in the future can make business a bit more open to the idea of 'wasting' time with a refractor.
But the real question, it is the true reason you are doing this refactor?
or it is a cover-up?
Yes and no. I want to refractor because the code base is terrible to try and understand. It takes far too long to walk through. A refractor will keep me from taking a week to understand the flow which will save money. Personally I'm more concerned by the headache of trying to follow the code flow.