Lesson151 - Software Architecture Roles and Titles

[@rawberry3]

Great lesson as always, thanks Mark. I agree with your general positionings here, having started out in Technical Architecture, then moving into Solution Architecture and likely to Domain Architecture in 2023. I'd like to address all aspiring or existing architects to never forget that YOU determine what kind of architect you want to be - not titles or traditions or companies. You have the power to shape your own role to make it mean what makes sense for you and for your company - and if you want to be a different kind of architect you can mould yourself and your role (with a bit of extra work, don't let the task at hand slide!) The title will eventually catch up!

[@markrichards5014]

Well said!

[@fuzzy0001]

Hi Mark, please make one video on Headless Architecture, thanks,

[@thedeveloper2513]

Thanks Mark, I've always wondered what the difference was between those titles and it now makes sense.

[@SteveLeve]

Thanks for this explanation Mark, mostly aligns with what I've seen elsewhere. I've been on this journey of definition since before my org promoted me to the role of "Architect" (without any qualifier) and I've scrambled to carve a definition & boundaries into this role since. It seems like everyone I encounter has a different definition & set of expectations! I have responsibilities from all over the map, so I'm going with SA!

[@mohamedboufnichel6187]

Amazing content as usual Thanks a lot Mark

[@kamalbakarim3385]

Hello Mark and thank you so much for your excellent explanation. I've a question about the modern system integration still we need to use a ESB to integrate legacy and modern apps or not?

[@markrichards5014]

Great question! I'll answer it by doing a lesson on your question for February. Thanks!

[@Baklava_daddy]

Thanks Mark for the lesson. This has been helpful, what about Functional architect?

[@markrichards5014]

Now that's a title I haven't come across yet - but, how would that differ from a product owner I wonder?

[@gagyboki799]

HI Mark, great video as always. Back in your time, when you started with Software Architecture, I guess there was only 1 title? How do you find this kind of title explosion for architects? How would you suggest structure to look like if you had your way? I think that many of titles and roles can be joined into single title.

[@markrichards5014]

I so agree! Unlike the medical field, I'm not convinced we have that level of specialization yet. It would be nice to at some point be able to have some industry-standard titles for a software architect.

[@MarusykRoman]

what about "Software Architect"?

[@markrichards5014]

LOL! I suppose that would be the same as saying "I'm a doctor". A doctor of what? medicine? philosophy? What specialization? In other words, that title is usually a catch-all for all the possible roles in software architecture.

[@ashraffouad]

Thanks Mark for the lesson. I think maybe the title of the video should be "IT Architecture ..." instead of "Software Architecture ..."