How would you balance between designing and (actually) implementing your application

Question

My question is not a programming language, but its more general question to understand how people think.

Typically, large development houses have specific roles for each job, such as programmers and architects. so that architects have a point of view to have an ideal design of architects and solutions, on the other hand, programmers are engaged in the implementation of application functions and interface elements. Therefore, if you allow the architect, for example, to work with the application without programmers, you will get a great application from design (design patterns, classes, database tables), but nothing from the outside, it also applies the other way around. Programmers always focus on exiting without paying too much attention to design principles (e.g. SOLID ).

Now I am working on a small company with a team of 8-10 people, so you need to take care of the design of your application, as well as the implementation of functions. Therefore my question is just

• when do you need to stop developing and implementing your solution?
• or should there be incremental work?
• What if you reached the point where you screwed up, just because you didn't design well from the start?

I hope we can have different ways of thinking, so we can offer many acceptable solutions.

Answer 1

/ . , , , , , . - ( - , , ..).

, , , , , - , , . , , , .

, , , , , . . , " " , , - . , , , , , , , .

, , , , , , , , ( ) , . , .

Answer 2

. , , , .

: No battle plan survives contact with the enemy. , . , , .

. , , , , , . - , , , .

, - , . , , .