My definition of legacy code comes from an interesting interview Michael Feathers gave at dZone. He defines legacy code as “code without tests”. And I bet, there is a lot of that stuff out there. But what if you decided to develop test-driven in the meantime? Should you leave the legacy code as it is? If you still want to use it, the answer is of course NO. But how could you make this good old big ball of mud better maintainable? Continue reading “Migrating legacy code to maintainable code with tests” »