is always precious so there is no point in refactoring what is already working. • We need refactoring only for the code which is not working as it should (slow, flawed, buggy, etc). • Which brings me too legacy code
code inherited from an older version of the software. A y code that was writte a couple of o ths ago is a legacy code. – by me code is legacy code as soon as it's written. – from stackoverflow
the requirements of the code you are going to work on before you start browsing the code. • Checkout the test cases that have been already added if any. • Assess which are the important parts, so that you can cover them first.