Which design template is best for iterative development?

Question

Is there such a thing as the most preferred design pattern for creating applications in TDD or iterative mode?

Answer 1

I think this question can be rewritten, so these words make more sense:

"What architectural patterns and strategies are useful for achieving flexibility when using a test and incremental development strategy?"

My answer: templates to help you separate your clans and components, for example:

• - , , , ( ), , .

• - , , .

• - , .

, " , " . .

, ?

Answer 2

, . , , , . !

:

• . .
• . , , . : " , , !".
• . ZOMG--- ----program-and-whatever. , , .
• , ( ). , , . - . , , " , ", " ", " ".
• DRY - . , . , .

Answer 3

, . ...

, , , (, ): Ron Jeffries, " ".

: , Bridge. . , . "F".:)

Answer 4

- , . , , .

Answer 5

Use a dynamic language such as Python or Ruby: you don’t have to deal with many of the problems that other languages ​​face that cause “design patterns” in the first place.

Dynamic languages ​​combined with automated testing will produce results very quickly so that you know which direction to go. If you understand that you should use a static language for performance reasons or whatever, you can translate the already created dynamic software.