Hacker News new | ask | show | jobs
by rmanolis 564 days ago
The best way to architect, test and develop software
1 comments

Can you describe how this is different from TDD.

From what I understood it seemed like you listed a collection of requirements for TDD failure cases, named them "can't" statements and then did TDD on them. But I believe there is more to it, but I couldn't see it.

Could you list the types test cases you would have created if you had done TDD on this same problem? And how they'd be different?

In TDD, I would have to iterate over the hello_from procedure 900 times to create the software design.

In CDD, I created first the software design by translating "can't" statements to errors and then iterate over the errors following specific rules to create a tree of stack traces that created the software design and then I TDD over that design to complete the application.