I can’t find the translation.
Answer 1, authority 100%
Answer 2, authority 77%
Summing up all the definitions that have been encountered, I have derived the following for myself.
Legacy code – a code that matches one or more features:
- was written by other developers,
perhaps no longer available to
- not covered by unit tests;
- retained for compatibility with previous versions of the system;
- is deprecated and / or is no longer supported due to system development (written in the previous language, for the old architecture, hardware platform, operating system, etc.).
Answer 3, authority 38%
The requirement for “experience working with legacy code” in a vacancy means that you will get code written 10-20 years ago by long-quit programmers. It is possible that it was initially poorly written, that the requirements for the project had changed many times and each time the code was corrected as needed in the tight deadline mode, that no one wrote the documentation and did not refactor it. Therefore, instead of writing new code using progressive technologies, most of the time you will have to understand the old one and correct it, then catching cascades of bugs. Welcome to the wonderful world of the bloody enterprise, the main consumer of Java.
Answer 4, authority 21%
There is also a “inherited legacy code” that no one knows how it works. Only a programmer is unlikely to help here – either an analyst is needed here, or data scientist , and the programmer is the maximum he can, it is an interface for them to write, if it is not there, that is. That is, to display on the form what is possible from what is in the code.