concept risk in category legacy software

appears as: risk, risk, risks, risks
Re-Engineering Legacy Software

This is an excerpt from Manning's book Re-Engineering Legacy Software.

Because of this lack of information, many teams come to respect the status quo as the safest option, and become fearful of making any unnecessary changes to the software. Any change is seen purely as a risk, and the potential benefits of changes are ignored. Thus the project enters a kind of stasis, whereby the developers expend most of their energy on maintaining the status quo and trying to protect the software from all externalities, like a mosquito trapped in a blob of amber.

Refactoring can also lead to regressions, but the risk is generally lower. A disciplined refactoring in which you perform a sequence of small, well-defined transformations (some of which we’ll look at in the next chapter) against an existing codebase should in theory preserve the behavior of the software. After each step of the refactoring you can stop, perform code reviews, and run automated tests to check that the behavior hasn’t changed before moving on to the next transformation. In a rewrite, on the other hand, you’re starting with nothing and attempting to build something that perfectly emulates the behavior of the original software. Which do you think is easier: taking the ceiling of the Sistine Chapel and swapping some of the frescoes around, or trying to recreate Michelangelo’s handiwork from scratch?