Read "Refactoring to improve the design of existing code" background

October 09, 2018

First of all to explain the background, the reason why they have a spontaneous motive to see the professional books, or forced to work.

From 2013, the company's software project construction "Great Leap Forward", on hand to accumulate a 15 is not small but also little industry information management system needs to be maintained. Each system user has 500 to 600 users, the peak is Be people online operation. Software system is for the industry in the Brother Unit/company, running in the internal 10 network, not facing the broad masses of the internet, so there is no concurrency and reliability, no special strict requirements. But if a feature is not available, or if the server goes down, midnight calls are still unavoidable.

The system was created in 2013, using the Java Web at the time of the popular Spring3 + Struts2 + Hibernate3 and MyEclipse8.5 + SVN. Early project belongs to groping stage, the personnel change is also big, no actual team leader, Nature also does not have the unified norm within the project, lead to incomplete document, code quality is not high, for later left more hidden trouble. Finally, all fell on their own body, and in addition to the old members have been lost, I took 2 new pits planted trees, deep inside the weak, so I want to find a relief method: reorganization code.

This is the motive for my reading this book.

Read "Refactoring to improve the design of existing code" background