Thanks, that was interesting. Of course we all (quite possibly instinctively) know the problems with legacy code, and by extension the crippling effect of tak

Thanks, that was interesting. Of course we all (quite possibly instinctively) know the problems with legacy code, and by extension the crippling effect of taking on the "agile / scrum" methodology without the unit testing side of the work. The "pay me later" side of the coin is so much less sexy. The story of IMVU is (I think) even more fascinating. I see your ads all over the place (and therefore assume you're successful) but it really is a case of "who the hell knew THAT would be successful. I mean - IRC with 3D avatars? Brilliant! :) (I oversimplify out of ignorance, not disrespect. I've never used the service, but assume it's very much loved by the target market). Test Driven Development and even just writing unit tests is so much less rewarding, because you can't say "see? look, I've made something new" - in fact - 99+% of the time, they're really just about proving 1+1=2. Who gets excited by writing a test to tell you that the sky is up and apples fall down? It's only a few thousand lines of code in that that kind of validation and reassurance really starts to pay off. Once you get yourself that far into the matrix - you really need someone to tell you which way gravity falls. (Should I have gone with an inception reference instead? blah blah falling top)