An External Replication on the Effects of Test-driven Development [pdf]

Re:An External Replication on the Effects of Test-driven Dev... by shubhamjain on Wednesday October 19, 2016 @12:17AM (#12741031)

> 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/

[ Parent | on HN ]

Re:An External Replication on the Effects of Test-driven Dev... by madeofpalk on Wednesday October 19, 2016 @12:35AM (#12741090)

Reminds me of a comment by Harry Roberts on CSS methodologies https://twitter.com/csswizardry/status/539726989159301121

    Modularity, DRY, SRP, etc. is never a goal, *it’s a trait*.
    [...] understand that they’re approaches and not achievements.

[ Parent | on HN ]