Do I need to separately design the project architecture?

Question

Software design

I read almost everything here and on Habré about the architecture of the project. Its importance is obvious, especially the avoidance of errors at the initial stages of creation.
Would it be more correct to order a knowledgeable specialist to separately develop architecture, design, choice of technologies, rather than how the programmer will code based on his ideas?
Perhaps it is better to have a description of the architecture and, based on it, set programming tasks.

Answer 1

It is better for the programmer to draw the architecture himself, put it on display, get kicks, read it, and make a new version.
All the same to him to develop.

Answer 2

Depends on a very large number of factors. Most often, it is much better when an experienced developer is involved in the implementation, who can adjust the architecture on the fly. Well, it is often impossible to understand where the architecture ends and the implementation begins, so it is difficult to formulate the result of the work of a "knowledgeable specialist".

Answer 3

if you feel that your qualifications are not enough, then of course there is a point.
although it is better not to take on tasks that are two heads above your capabilities. it is better to complicate projects gradually.