4 ms·
Summary: This kind of architect must be very aware of what’s going on in the project, looking out for important issues and tackling them before they become a se
by jph 6y ago
Summary: This kind of architect must be very aware of what’s going on in the project, looking out for important issues and tackling them before they become a serious problem. The most noticeable part of the work is the intense collaboration. The architect raises the level of the development team so that they can take on more complex issues. [n.b. edited for clarity]
- lmilcin 6y agoI think the problem with definition of who is an architect is the fact everybody wants to have a job description. My understanding is that architect is somebody who decides which details are interesting and important to him and which are not. A lot will depend on the project and its environment. In my current project the team may need a little bit help so I do stuff like define more important internal APIs or migration paths. I also typically do it in form of pair programming to get to know people and have occasion for discussion, to up their level a little bit if possible. In another project the team would get much more freedom and I would be having more teams with shallower view. One thing that an architect should be doing is being responsible for overall health of the application and development process. Right architecture and approach to problems can solve a lot of problems and an architect that just blames other for problems and spends time preaching new fantastic shiny frameworks is no architect at all.