Agreed, I think it's important to bear in mind the "time value of code". Some code may very well be "set and forget" - you write it once and noone ever looks a

Agreed, I think it's important to bear in mind the "time value of code". Some code may very well be "set and forget" - you write it once and noone ever looks at it ever again. If a project is allocated 100 days, why invest even 1 of those refactoring and polishing code that really doesn't need it? The difficulty, of course is knowing which code is 'set and forget' and which isn't. I usually avoid refactoring until you hit the same "how does this work again?" wall at least three times.