> But don't force it down my throat or act like it's the One True Path to clean code. When I was a programming beginner and started learning about TDD, I was

> But don't force it down my throat or act like it's the One True Path to clean code. When I was a programming beginner and started learning about TDD, I was always thinking how soon to start using it because everyone says it's such a good idea. If you would search anything about it, you'd rarely find a resource not marvelling at its surprising benefits (at least, that is how it was few years back). Granted, it may have its merits but is it really a good idea for everything? No way! One of the anti-patterns I have seen in programming world is how everyone jumps on adopting / advocating a 'good' practice without understanding how it fits the project. I wrote about this a while back[1]. Cue in — git flow, TDD, not using goto, DOM Parser instead of RegEx. [1]: https://shubhamjain.co/2015/10/26/imperfect-best-practices/ https://shubhamjain.co/2015/10/26/imperfect-best-practices/