Artwork

Content provided by O'Reilly Media. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by O'Reilly Media or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.
Player FM - Podcast App
Go offline with the Player FM app!

Nathaniel Schutta on succeeding as a software architect

29:52
 
Share
 

Manage episode 191712989 series 1433313
Content provided by O'Reilly Media. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by O'Reilly Media or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.

The O’Reilly Programming Podcast: The skills needed to make the move from developer to architect.

In this episode of the O’Reilly Programming Podcast, I talk with Nathaniel Schutta, a solutions architect at Pivotal, and presenter of the video I’m a Software Architect, Now What?. He will be giving a presentation titled Thinking Architecturally at the 2018 O’Reilly Software Architecture Conference, February 25-28, 2018, in New York City.

Discussion points:

  • How Schutta sees the role of the software architect: “I like to say that as architects, we’re like the Rosetta Stone of an organization,” he says. “We’re the ones playing the translation game between the development side, the management side, and the business side. We have to be able to fit comfortably between those groups.”

  • On the challenges in moving from being a software developer to becoming a software architect: “As developers, we’re largely insulated from much of the politics of the organization,” Schutta says. “As an architect, you have to craft your message for many different audiences, and take the core central idea and spin that yarn so it resonates for all these groups.”

  • The “soft skills” that are needed to succeed in the architect role, including communications, leadership ability, self-promotion, and investing in personal relationships.

  • How to “think architecturally”: “As developers, we have this tendency to chase the shiny new thing, but as an architect, we can’t afford to do that,” Schutta says. “The decisions we make have long-lasting impact, so architects have to be thinking about trade-offs.”

Other links:

  continue reading

25 episodes

Artwork
iconShare
 
Manage episode 191712989 series 1433313
Content provided by O'Reilly Media. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by O'Reilly Media or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.

The O’Reilly Programming Podcast: The skills needed to make the move from developer to architect.

In this episode of the O’Reilly Programming Podcast, I talk with Nathaniel Schutta, a solutions architect at Pivotal, and presenter of the video I’m a Software Architect, Now What?. He will be giving a presentation titled Thinking Architecturally at the 2018 O’Reilly Software Architecture Conference, February 25-28, 2018, in New York City.

Discussion points:

  • How Schutta sees the role of the software architect: “I like to say that as architects, we’re like the Rosetta Stone of an organization,” he says. “We’re the ones playing the translation game between the development side, the management side, and the business side. We have to be able to fit comfortably between those groups.”

  • On the challenges in moving from being a software developer to becoming a software architect: “As developers, we’re largely insulated from much of the politics of the organization,” Schutta says. “As an architect, you have to craft your message for many different audiences, and take the core central idea and spin that yarn so it resonates for all these groups.”

  • The “soft skills” that are needed to succeed in the architect role, including communications, leadership ability, self-promotion, and investing in personal relationships.

  • How to “think architecturally”: “As developers, we have this tendency to chase the shiny new thing, but as an architect, we can’t afford to do that,” Schutta says. “The decisions we make have long-lasting impact, so architects have to be thinking about trade-offs.”

Other links:

  continue reading

25 episodes

All episodes

×
 
Loading …

Welcome to Player FM!

Player FM is scanning the web for high-quality podcasts for you to enjoy right now. It's the best podcast app and works on Android, iPhone, and the web. Signup to sync subscriptions across devices.

 

Quick Reference Guide