Architecture at large scale, such as in enterprises and organisations with complex infrastructure, puts very different demands on the role than being a software engineer or even solutions architect. For sure, you will need solid technical skills. But the ability to convince and drive solutions become more and more important. 

In this episode I talk to three ex-colleagues of mine from Elsevier - who have been working as enterprise architects for some time. And we touch on the challenges of the role and how they deal with it.

Links you may want to follow up on:

- Lean Software Architecture http://www.leansoftwarearchitecture.com

- Melvin Conway's paper: "How do committees invent?" http://www.melconway.com/Home/Committees_Paper.html

- Conway's Law: http://www.melconway.com/Home/Conways_Law.html

Get in touch

Thank you for listening! Merci de votre écoute! Vielen Dank für´s Zuhören!

If you're like to support this show, you can leave a little tip at

https://en.tipeee.com/code-for-thought-podcast/

Contact Details/ Coordonnées / Kontakt:

• Email mailto:[email protected]
• UK RSE Slack (ukrse.slack.com): @code4thought or @piddie
• US RSE Slack (usrse.slack.com): @Peter Schmidt
• Mastodon: https://fosstodon.org/@code4thought or @[email protected]
• Bluesky: https://bsky.app/profile/code4thought.bsky.social
• LinkedIn: https://www.linkedin.com/in/pweschmidt/ (personal Profile)
  • LinkedIn: https://www.linkedin.com/company/codeforthought/ (Code for Thought Profile)

This podcast is licensed under the Creative Commons Licence: https://creativecommons.org/licenses/by-sa/4.0/