Artwork

Iasa Global에서 제공하는 콘텐츠입니다. 에피소드, 그래픽, 팟캐스트 설명을 포함한 모든 팟캐스트 콘텐츠는 Iasa Global 또는 해당 팟캐스트 플랫폼 파트너가 직접 업로드하고 제공합니다. 누군가가 귀하의 허락 없이 귀하의 저작물을 사용하고 있다고 생각되는 경우 여기에 설명된 절차를 따르실 수 있습니다 https://ko.player.fm/legal.
Player FM -팟 캐스트 앱
Player FM 앱으로 오프라인으로 전환하세요!

Is You Is or Is You Aint An Architect

1:01:35
 
공유
 

Manage episode 302495129 series 2910526
Iasa Global에서 제공하는 콘텐츠입니다. 에피소드, 그래픽, 팟캐스트 설명을 포함한 모든 팟캐스트 콘텐츠는 Iasa Global 또는 해당 팟캐스트 플랫폼 파트너가 직접 업로드하고 제공합니다. 누군가가 귀하의 허락 없이 귀하의 저작물을 사용하고 있다고 생각되는 경우 여기에 설명된 절차를 따르실 수 있습니다 https://ko.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 에피소드

Artwork
icon공유
 
Manage episode 302495129 series 2910526
Iasa Global에서 제공하는 콘텐츠입니다. 에피소드, 그래픽, 팟캐스트 설명을 포함한 모든 팟캐스트 콘텐츠는 Iasa Global 또는 해당 팟캐스트 플랫폼 파트너가 직접 업로드하고 제공합니다. 누군가가 귀하의 허락 없이 귀하의 저작물을 사용하고 있다고 생각되는 경우 여기에 설명된 절차를 따르실 수 있습니다 https://ko.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 에피소드

Все серии

×
 
Loading …

플레이어 FM에 오신것을 환영합니다!

플레이어 FM은 웹에서 고품질 팟캐스트를 검색하여 지금 바로 즐길 수 있도록 합니다. 최고의 팟캐스트 앱이며 Android, iPhone 및 웹에서도 작동합니다. 장치 간 구독 동기화를 위해 가입하세요.

 

빠른 참조 가이드