I have heard that many developers call codes as "inheritance" most of the time this code is written by a person Has no longer worked on the project. What is this code, which makes the inheritance code?
The answer in the update: "Below are some ancestors or predecessors or past", clearly, you wanted to know more, can you clarify or expand your question? s. Lot
I am looking for symptoms of inheritance code which makes it unusable or makes a nightmare to work with. When is it better to throw it off? It is my opinion that the code should be thrown more often and replacing the wheel is an important part of development.
On the other hand, the legacy code is clearly worth keeping.
using hardware, software, API, languages, techniques or features that are no longer supported Or superseded, usually there is a small chance that instead of replacing that code, it is a til or a system die
Comments
Post a Comment