A question has been raised about the future of the architect role with the rise of AI. If human-built software (and SaaS, as claimed by Microsoft’s CEO) is going away, what happens to the practice of architecture?
I’m rarely optimistic (the curse of architecture, I guess), but I feel safe.
...
If, after quitting your job, you hear or get notified about your ex-leader doing these :
Speaking negatively about your departure Undermining your decision by criticizing you, your new role or company Attempting to make you feel guilty Spreading resentment throughout the organisation Taking the resignation as a personal attack Prioritizing their own interests over those of the team Being absent or unavailable for the team during the transition Spreading gossip about you Delaying or writing vague performance appraisals or recommendations for you Displaying an “it’s all about me” attitude Failing to acknowledge their own mistakes or shortcomings Blaming others for failures or problems within the team These behaviours scream insecurity, selfishness, and a lack of confidence in building and retaining talent. They crush team morale, erode trust, and send a clear message to the rest of the team: ‘You’re disposable too.’
...
Being an Architect is like being a conductor1 in an orchestra. You’re not playing all the instruments, but your job is to make sure everyone is in concert [pun intended] and that the result is harmonious.
I once saw Simon Rattle conducting 6 Berlin school orchestras playing Edvard Grieg’s Peer Gynt Suite. As a matter of fact, they never worked nor rehearsed together before. Their first play was awful and cacophonic, but after multiple corrections and rehearsals, Rattle transformed the final performance into a beautiful and majestical piece.
...
After a heavy lunch break with a team, Dorian, one (among others) young and competent developer, enthusiastically asked me: “How does someone become an Architect, and what’s the path to follow and what to learn to be one?”
I wasn’t asked this question for the first time, and to be honest, I was never able to answer it properly.
...
The role of the software architect remains a subject of considerable debate: it is vaguely defined, difficult to pin down, and sometimes leads to nonsensical responsibilities in certain job descriptions.
I will not discuss here the precise day-to-day responsibilities of an architect within a team or company, but I will attempt, through my experience, to describe some of the aspects and qualities that any architect should possess.
...
