From the perspective of technical debt, talk about reconstruction

First, what is meant by reconstruction (Refactoring)?

It is Definitions: The software for adjusting the internal structure , aimed at changing the software without observable behavior , improve reliability , reduce cost modifications thereof .

So reconstruction in our eyes it should look like this

On technical debt (Technical Debt):

Development team in the design or architecture selection, from the perspective of short-term effects of a selected program easy to implement. But in the long term, this program will bring more negative impact on the debt that is owed by the development team.

Simply put, it is to solve the problem quickly, and take non-standard solutions, thus worse retribution, ha ha.

Technical debt may cause we can not expect to deliver projects

for example

For the mortgage, I am sure you all remember a month still to go.

However, for technical debt, so we do not seem to care.

For example, a white student in a class owed in the technical debt, for example, wrote a 15-line 300 large method parameters are not the responsibility of a few weeks after he extend this class, modify, boss reminder of the urgency, the wrongs, final: a 20 parameters, super perverted method 600 lines produced.

However, this thing is not necessarily who borrow who might be one thing, it could be a team thing,

Let us assume it: this white students left the company .....

So, the debt on the pressure in the body of work of a successor, the ancient language: Father son subordinated debt, then this should be called: TM so and so love it .........

Before long, the entire development team will find that we have been unable to repay this debt technical matter, it can only be reconstructed, and the reconstruction is part of the most difficult, the most costly way to a reconstruction, planned reconstruction (Planed refactoring) , which is the reconstruction plan will have to be added to the product backlog inside.