Re: Working with Legacy Code

On 12 Jul, 22:49, andrewmcdonagh <andrewmcdon...@gmail.com> wrote:
> On Jul 12, 8:00 pm, Alistair <alist...@ld50macca.demon.co.uk> wrote:
> 
> 
>
> :)
>
> I know what you mean.
>
> However, having read the book and talked to the author (he's a regular
> on Agile software development lists (extremeprogramming,
> testdrivendevelopment (TDD), refactoring, etc) I can clarify what he
> means by 'legacy'.
>
> To Micheal, any code that does not have automated unit tests, is
> Legacy Code.  Even code written 10 mins ago.
>
> It can be an odd statement, but in the context of Agile, TDD etc,
> Automated unit tested code is a major important  deliverable.
>
> The aim of this book is to help developers understand how to retrofit
> unit tests to EXISTING code that does not already have them, hence the
> term Legacy.
>
> HTH
>
> Andrew

That does take the wind out of my sails a bit.