Today’s Heavy Networking is the result of a listener request. We discuss the differences between network architects and network engineers.

What’s different about each role? Where is the overlap? If you are an architect and find yourself doing engineering, is that a bad thing?

Should an engineer aspire to be an architect? Are architects so out of touch with reality that engineers rightfully hate them?

If an architect and an engineer pass each other in the hall, does the engineer have to kiss the architect’s ring every time, or just the first time?

To answer these questions, we’ve gathered guests who’ve held both roles in their careers (as has your host).

Our guests are Robin Gilijamse, IT Infrastructure Architect; Oli Elliott, Network Architect at the University of Bristol; and Tom Ammon, Sr. Network Architect at a regional service provider in the United States.

We talk about:

* The definitions of an engineer and an architect

* The path to becoming an architect

* The perspective of tactics vs. strategy

* Whether you have to give up hand-on networking

* Why architects have to get more deeply involved with business requirements and nurture personal relationships

* Advice for folks new to the architect role

Sponsor: INE

If you’re looking for training, consider INE.com. INE is a training resource for networking and a whole lot more. Visit ine.com/packetpushers to get a free 3-day trial. INE–experts at making you an expert.

Sponsor: Open Systems

Open Systems brings security, automation, and expert management to SD-WAN. Get visibility, flexibility, and control combined with performance, simplicity and security with SD-WAN from Open Systems. To find out more, go to Open-systems.com/packetpushers and get a free beanie and a Gartner report on the economics of SD-WAN.

Show Links:

Robin Gilijamse’s blog “Interesting Traffic”

Tom Ammon’s blog