---
title: "Comment by Julian Ewers-Peters on \"Why I Don't do TDD\" | Hashnode"
description: "TDD at its core is not about testing, it's about how to approach better code design. The idea is to think about the required structure of your code before y"
url: "https://hashnode.com/posts/why-i-dont-do-tdd/6373af8a4a2eb420e8853ec0/comment/63764a91f0820773cfb15732"
---

[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)

[Julian Ewers-Peters](https://hashnode.com/@ewerspej)

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

TDD at its core is not about testing, it's about how to approach better code design. The idea is to think about the required structure of your code before you write it, based on incremental steps. TDD only looks at the public interface and thus is compatible with unit and integration testing. I believe that many people have a misconception of what TDD is. Andrea Laforgia has an interesting view on this: [dev.to/andrealaforgia/why-test-driven-design-386c](https://dev.to/andrealaforgia/why-test-driven-design-386c)

[Shai Almog](https://hashnode.com/@codenameone)

[Nov 22, 2022](https://hashnode.com/posts/why-i-dont-do-tdd/6373af8a4a2eb420e8853ec0/comment/63764a91f0820773cfb15732#reply-637cf1fa144aebc44d19302e)

I have a paragraph specifically about that point. It doesn't make much sense either. You can't debug a design but visually you can understand it. So it isn't great but it's clear.

You can't "test the tests". So you have a "design by tests" that hardcodes the bugs but isn't clear as a design.