While I have become a proponent of TDD and have come to appreciate it in larger projects, I agree and remember the tediousness of it as a beginner.. It is good to inform the beginner of its style and merits, but not to enforce it -- rather let them decide for themselves if it helps them and their team in the long-run; experience is a far superior teacher
I think that as long as the code you commit has full coverage and good quality tests (not only tests to improver coverage) then testing your code after writing it can be equally effective in large projects.
I guide many junior developers and find that TDD is just too much to enforce while learning.
