The article is aimed at dialogue about the need for an architect in a team. It will be of interest to those who are thinking about the path of their development, when βall the roads have already been walkedβ. When a wealth of experience makes your job βineffectiveβ from the point of view of your colleagues. When almost nothing surprises you and every next project is deja vu. You burn out.
What is an architect?
Everyone can Google on this topic independently. I will try not to be a cap and reflect the essence of the architect from an unusual angle. Personally, I like the humorous definition of this role:
β , , .
:
β , .
, :
- ;
- - .
. () , ? . , ++ . , .
, . -. . β¦.
, ? :
- ;
- , .
, . , , . , .
, - . , , .
, :
- .
, , , , , ( ), .
?
, . -, .. , .
. , .
, . .. . . , . .
, . , , . , . .
. , . .. . . . . , ( ), . . . .
, - . . β .
, , , , . . , . , - β . , () . .
. , . . , , . . , , .
ββ . - . , , . :
- React! !
. . . , React , , .
. React . . . , React . React. . .. .
. . .
, β β. , , , . . . .
. , , . , .
, , .
?
, β .
.. . .
. - , , β¦ .
, , . - , , . . . . . . , . . .
β . , , . , . . . , , .
, , .
, , .
, . , , . , . , .
, . β , , . .
. . .
, . . -, , , , ( ) -.
?
. . :
- , ;
- ;
- .
β ββ. ? - CTO. . , , . .
:
- ;
- ;
- ;
- .
- ...
:
- ;
- ;
- ;
- ;
- ...
? , .
: ->->->->CTO. - , , - . β . . .
, , , . , , , pet-. .
, . , . , . . .
? : .
Instead of a conclusion
I propose to talk about the need for an architect in a team. How do you imagine his role? Have you faced the need for it? Perhaps on the contrary, he was disturbing you? Do you see yourself as an architect in perspective? Would you like to change the path of a manager to that of an architect? Would it make you happier?