To literately quote myself from last week during a software development meeting: "No, refactoring will never end."
It should be the software developer's mantra, or ABC: "Always Be Correcting."
Software development is probably one of the scariest sciences/engineering disciplines. It is a really young field with a tremendous acceleration which has never been observed in any other field. When we talk about "old" we talk about 5 years ago (this used to be 10 years). Why is it scary? The changes the industry goes through are too fast and quite uncontrolled, and they spread wider and wider.
The code you look at, which you need to modify, which is only 5 years old. It needs to be brought up to code before you can start changing it. What is means is simple, you need to refactor so that it can be changed. But that's the complicated part. It probably doesn't have good unit tests covering it properly. So you first have to ensure that the effective behavior gets defined by writing unit tests. Then you can start changing the code to make it usable for modification. Plain and simple, just a few days of work...
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.
To literately quote myself from last week during a software development meeting: "No, refactoring will never end."
It should be the software developer's mantra, or ABC: "Always Be Correcting."
Software development is probably one of the scariest sciences/engineering disciplines. It is a really young field with a tremendous acceleration which has never been observed in any other field. When we talk about "old" we talk about 5 years ago (this used to be 10 years). Why is it scary? The changes the industry goes through are too fast and quite uncontrolled, and they spread wider and wider.
The code you look at, which you need to modify, which is only 5 years old. It needs to be brought up to code before you can start changing it. What is means is simple, you need to refactor so that it can be changed. But that's the complicated part. It probably doesn't have good unit tests covering it properly. So you first have to ensure that the effective behavior gets defined by writing unit tests. Then you can start changing the code to make it usable for modification. Plain and simple, just a few days of work...