---
title: "Comment by Mikalai Kardash on \"Compile the C test runner\" | Hashnode"
description: "I love how everything unfolds in a series of TDD cycles. Great work! Looking forward to the deep dive about those macros."
url: "https://hashnode.com/posts/compile-the-c-test-runner/6599fd5477b624d3cc32f815/comment/659d364e822347bbc290f349"
---

[Discussion](https://hashnode.com/posts/compile-the-c-test-runner/6599fd5477b624d3cc32f815)

Comment [Compile the C test runner](https://hashnode.com/posts/compile-the-c-test-runner/6599fd5477b624d3cc32f815)

[Mikalai Kardash](https://hashnode.com/@mkardash)

[Jan 9, 2024](https://hashnode.com/posts/compile-the-c-test-runner/6599fd5477b624d3cc32f815/comment/659d364e822347bbc290f349)

I love how everything unfolds in a series of TDD cycles. Great work! Looking forward to the deep dive about those macros.

[Warren Markham](https://hashnode.com/@WarrenMarkham)

[Jan 9, 2024](https://hashnode.com/posts/compile-the-c-test-runner/6599fd5477b624d3cc32f815/comment/659d364e822347bbc290f349#reply-659dcd4d4e7b11fc231b9ac5)

Thanks for the encouragement! I'm definitely drawn to TDD. I like that it encourages problem-solving techniques that echo processes we might recognise as part of 'doing science':

-   small, controlled steps
-   asking specific questions to get specific answers
-   record keeping
-   controlling variables
-   valuing evidence over guesses
-   documenting knowledge (in tests) so that the outcome can be collaborative and incremental
