Answer the question
In order to leave comments, you need to log in
How do you deal with legacy code on large projects?
Good afternoon colleagues!
I would like to know the public opinion about the heritage of the code. It is no secret to anyone that large projects that have been developed for many years are often greatly overcomplicated in their structure, architecture, with the help of a "technology zoo", etc. And if you dig deeper, you can often stumble upon a frank govnokod, but it works.
Often this situation comes up: the code is terrible but it works, and refactoring is even more scary than the code.
How do you solve such a problem?
Answer the question
In order to leave comments, you need to log in
No amount of code should be intimidating if the budget is allocated for it.
If it does not stand out, then refactoring for the sake of refactoring is not needed.
If the client needs the program, then just take it and conduct an investigation - which will be better and more profitable in the long run - large-scale refactoring or writing from scratch. If the price suits, the terms are determined, people are hired. In general, it doesn't scare you.
Development through testing (the presence of tests) gives at least some guarantee for the architecture of your application that it will not change if another person comes to the place of the application creator.
vasIvas @vasIvas
Can you explain how tests help to get rid of bad code and, moreover, of incorrect architecture?
Written March 03
Reply
Nc_Soft @Nc_Soft
vasIvas: no way
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question