in reply to Re: Code Structure Changes
in thread Code Structure Changes

I would write tests first to confirm the behavior of the parts I think should change.

Having been bitten by such things too many times I would suggest that you ensure 100% coverage of the tests before changing anything. It is far too easy to think that you've covered all the parts you intend to change without finding all the downstream traps. That said, I agree wholeheartedly with the rest of your post.