I like to think of software as a living entity that grow evolve, get sick and eventually die. There is nothing wrong with refactoring or diying code it's part o

I like to think of software as a living entity that grow evolve, get sick and eventually die. There is nothing wrong with refactoring or diying code it's part of the natural process of engineering software. Sometime we take the decision to not refactor, that's also ok as long as you know that this will make cost you more to do it later or will code will end up diying. Your code is like a pet, his love depend on how much effort you put to take care of him. Sometime, it's sick by design and where ever effort you put in won't save it. So now if we talk about how to design software that will live long and prospere you need to guess/predict the future and have an idea on all the forms that your software will evolve to and all the intented and non intended use possible for it and avoid all mistakes in you design and then you will have a warranty otherwise you need to design the simplest way and make it evolve when needed by refactoring, fixing and patching...