Artwork

Contenu fourni par Iasa Global. Tout le contenu du podcast, y compris les épisodes, les graphiques et les descriptions de podcast, est téléchargé et fourni directement par Iasa Global ou son partenaire de plateforme de podcast. Si vous pensez que quelqu'un utilise votre œuvre protégée sans votre autorisation, vous pouvez suivre le processus décrit ici https://fr.player.fm/legal.
Player FM - Application Podcast
Mettez-vous hors ligne avec l'application Player FM !

Is You Is or Is You Aint An Architect

1:01:35
 
Partager
 

Manage episode 302495129 series 2910526
Contenu fourni par Iasa Global. Tout le contenu du podcast, y compris les épisodes, les graphiques et les descriptions de podcast, est téléchargé et fourni directement par Iasa Global ou son partenaire de plateforme de podcast. Si vous pensez que quelqu'un utilise votre œuvre protégée sans votre autorisation, vous pouvez suivre le processus décrit ici https://fr.player.fm/legal.

The software or solution architect often comes from an engineering background. In this episode Cormac Keogh and Paul Preiss speak about the relationship between engineers. In a true argument the case of engineers, teams and architects. Can or should an engineer be the architect for a product/project? The team? Is there a difference between a titled architect and engineer? How do they work together?
In our research over the years one of the most critical paradoxes is the continued confusion over the boundaries between architect, engineer and developer. I separate these into three even though there is no industry-wide adoption of particular boundaries. For the purpose of this argument think of developers as self-taught and focused on smaller problems (no I don't mean title I mean competency!), engineers as trained and mentored but focusing on systemic structural elements and architects as outcome driven, trained and mentored creative and innovation focused with strong overlaps in depth skills with their counterpoints at certain points but with a focus on breadth and rounded out competencies.

  continue reading

28 episodes

Artwork
iconPartager
 
Manage episode 302495129 series 2910526
Contenu fourni par Iasa Global. Tout le contenu du podcast, y compris les épisodes, les graphiques et les descriptions de podcast, est téléchargé et fourni directement par Iasa Global ou son partenaire de plateforme de podcast. Si vous pensez que quelqu'un utilise votre œuvre protégée sans votre autorisation, vous pouvez suivre le processus décrit ici https://fr.player.fm/legal.

The software or solution architect often comes from an engineering background. In this episode Cormac Keogh and Paul Preiss speak about the relationship between engineers. In a true argument the case of engineers, teams and architects. Can or should an engineer be the architect for a product/project? The team? Is there a difference between a titled architect and engineer? How do they work together?
In our research over the years one of the most critical paradoxes is the continued confusion over the boundaries between architect, engineer and developer. I separate these into three even though there is no industry-wide adoption of particular boundaries. For the purpose of this argument think of developers as self-taught and focused on smaller problems (no I don't mean title I mean competency!), engineers as trained and mentored but focusing on systemic structural elements and architects as outcome driven, trained and mentored creative and innovation focused with strong overlaps in depth skills with their counterpoints at certain points but with a focus on breadth and rounded out competencies.

  continue reading

28 episodes

Tous les épisodes

×
 
Loading …

Bienvenue sur Lecteur FM!

Lecteur FM recherche sur Internet des podcasts de haute qualité que vous pourrez apprécier dès maintenant. C'est la meilleure application de podcast et fonctionne sur Android, iPhone et le Web. Inscrivez-vous pour synchroniser les abonnements sur tous les appareils.

 

Guide de référence rapide