I think that attitude is great. I always move the code/libs forward alongside write it, and I a solo developer and code in several languages and maintain code.

I think that attitude is great. I always move the code/libs forward alongside write it, and I a solo developer and code in several languages and maintain code. This work great for example, with obj-c where things are moving fast and all the changes in some ways cut the size of the code. In fact, moving the code forward is very cheap in contrast to stick for too long then eventually the pain is too hard. I learn this when try to move a large codebase from .NET 1 to 2, in one single shoot. Months on this (and back them we are a team). HOWEVER, the idea is mark deprecated things, build bridges and do something like GO that could rewrite/upgrade itself.