Backward compatible and standards compliant?

Say you have an old code base that you need to maintain, and it clearly does not meet current standards. How would you extend your efforts to maintain backward codebase compatibility while achieving standards compliance? What is important to you?

+3
source share
2 answers

At my workplace, we don’t get time to refactor things just because it makes the code better. There must be an error or function request from the client.

Given this rule, I do the following:

When I reorganize:

If I need to make changes to an old project, I clean, reorganize or rewrite the part that I am changing.

, , .

, .

, , , .

:

, , . , . , .

:

, , :

:

  • , "" . , , , - .
  • , . , , .

- , , .

+4

, . / - , , .

+1

Source: https://habr.com/ru/post/1703553/


All Articles