---
title: "Comment by Sadra Yahyapour on \"Why I Don't do TDD\" | Hashnode"
description: "That&#39;s a great point of view Shai Almog ! I&#39;ve always been looking for opportunities to get my hands on TDD in practice by contributing to the open sour"
url: "https://hashnode.com/posts/why-i-dont-do-tdd/6373af8a4a2eb420e8853ec0/comment/6373e3d0d81a95516cadf650"
---

[Discussion](https://hashnode.com/posts/why-i-dont-do-tdd/6373af8a4a2eb420e8853ec0)

Comment [Why I Don't do TDD](https://hashnode.com/posts/why-i-dont-do-tdd/6373af8a4a2eb420e8853ec0)

[Sadra Yahyapour](https://hashnode.com/@lnxpy)

[Nov 15, 2022](https://hashnode.com/posts/why-i-dont-do-tdd/6373af8a4a2eb420e8853ec0/comment/6373e3d0d81a95516cadf650)

That's a great point of view [Shai Almog](https://hashnode.com/@codenameone)! I've always been looking for opportunities to get my hands on TDD in practice by contributing to the open source. To be clear, we always do a little TDD in our minds. We implement based on the way want to use the components. The first time I heard about that (TDD), that seemed so stupid to me! Why would I write tests first? What am I going to even test then? Over time, I thought that would be a cool approach though. You're structuring your components and specifying the ways you want to use your utilities then you implement them by passing each test. I still believe in that way of development but that DOES NOT ensure the quality of my code for sure. Of course, I need to refactor once I wrote the components. I'm more of a unit-test guy than an integration-test. Looking forward to having your thoughts on mine. Thanks for sharing this awesome article again. :)

[Sadra Yahyapour](https://hashnode.com/@lnxpy)

[Nov 15, 2022](https://hashnode.com/posts/why-i-dont-do-tdd/6373af8a4a2eb420e8853ec0/comment/6373e3d0d81a95516cadf650#reply-6373e88c747bca51e27ca0b4)

I also have an article about "How TTD helped me clean my code" drafted! LOL
