Comments on: TDD: No Fun, No Gain? Comments on: TDD: No Fun, No Gain? Consulting and Training for Software Teams By: jlangr Thanks Ray, That's where I started with TDD, in 1999--a bit smug about the fact that my code had almost no problems, and the other guys were always late with overly-defective code. So yes, if that helps others see the light, it's great. (JB Rainsberger suggests that it often doesn't generate the results we'd like, and I have to sadly agree with him: http://agile2007.agilealliance.org/downloads/handouts/Rainsberger_414.pdf). In 1999, the problem was that they didn't give a hoot about my tests, and at that time I had no way of incorporating them into the build. The other devs broke my tests and didn't care (despite my protestations). Nowadays, the problem I see in too many shops is that builds whose unit tests fail aren't considered "stop the line" by many teams. Jeff By: Ray <blockquote>Being the minority in a team, as I’ll relate in a later blog post through Tim’s stories, is a great way to lose that enthusiasm.</blockquote> Actually, my enthusiasm for TDD gets a big boost whenever other people on the team are struggling to get their code (that was supposedly already finished) working in a more realistic environment than their dev setup. Especially when I see them spend a lot of time debugging and when their fixes introduce new errors. Or when they spend a lot of time rewriting a whole bunch of code (because it doesn't allow for required change) and then have to go through a similar debug/fix/test cycle.