Role of the Architect
Вставка
- Опубліковано 15 вер 2024
- Juval Lowy discusses the role of a modern software architect. In addition to system design, the architect must also take an active leadership role on process and technology, and be the technical manager of the project. Juval explains how to become an architect and how the architect should manager his career, what are the skills required of the modern architect and the Architect's Master Class.
thank you this help me too see what I want to do in middle school so it can bring me up to high school then college(I'm going to a magnet middle school)
Were slides or a video for this presentation ever published?
"A good architect helps them with what to do, not necessarily with the how. The how they will figure it out." I deeply respect Juval, but I disagree with this statement.
The relationship between Architect and developer is fraught with tension. As Juval correctly notes, developers are content to copy code retrieved from a quick search. When Juval poses the question "How do you get developers to execute your design?", he demonstrates awareness of the threat that developers pose. The architect must protect the architecture. This gives rise to tension and perceived antagonism.
I maintain that the architect must provide developer support which leads the developer quickly to the better solution. That is, the developer helps the with the how in addition to the what. An architecture should make it difficult to do incorrect things. Then again, nobody asked me what I think (Exeunt).
It is wonderful to hear Juval speak about the Role of the Architect on the eve of the decline of this position.
a little too 'little'? i don't know how to interpret this but my gut feeling is that you don't respect the point i've made. i am most certain that we are not in agreement.
you are telling me what the architect does. i am telling that i have seen actual horror stories where there either was no Architect or there was an Architect but the architecture was undermined by developers who may have had the best intentions. and i am also telling you that i have seen actual situations where the Team Lead was making poor choices. in particular, several Scrum environments have wrestled with poor code-bases. it is in these environments that i have seen the Role of the Architect under attack.
finally, i wish to take issue with the claim that a concrete implementation for a particular detail won't change the architecture. if that developer were to introduce dependencies that should not be present, then i don't believe that this claim would be true. draw the architecture in layers and the arrows should go down. this is a heuristic that actually helps to control the orgy of interactions that would otherwise occur. but i have seen arrows that travel all over the place. and the Architect may have been unable to intercept this code prior to submission. then again, there may not have even been an Architect. but the damage was done.
so, i apologize for stepping on your toes. were you not trying to tell me that there was something i had not properly understood?
Mohd Nazmi, no. I thought about it. No peace. I don't say "peace" while simultaneously questioning someone's sensitivity and lecturing that person. No mixed messages. I am replying because I choose to. I told you what I had seen because I am asserting that this is the way it is in many shops. I corrected you because I don't believe that you know what you're talking about.