Should an Architect know about network and cabling?

[Rogerio Kioshi]

Do you think is important for an Architect knowing about network and cabling too?

[Akhilesh Trivedi]

Rogerio Kioshi wrote:Do you think is important for an Architect knowing about network and cabling too?

Do you mean social network or computer network or?

[Rogerio Kioshi]

Akhilesh Trivedi wrote:

Rogerio Kioshi wrote:Do you think is important for an Architect knowing about network and cabling too?

Do you mean social network or computer network or?

Computer network, even though I think sometimes architects must be more sociables, too.

[Ben Krokosky]

In my opinion those are separate skill sets and knoledge of one does not imply any sort of knowldeg of the other. To me architecture implies a deeper knowledge of network, protocols and software design and strategies. Cabling is sort of a technical detail.

That said too much knowledge is impossible. The more you know, the better!

-Ben

[fred rosenberger]

Would you expect an architect who designs a building to know how to run electrical wires?

It may be useful in understanding the bigger picture, but I don't think it is a requirement.

[Dave MacLean]

I like to say that a good architect knows the materials. While I might not expect a building architect to have experience pulling cables, I would expect a good building architect to know about steel, concrete, glass, etc. If you're going to architect networks, you probably need some hands-on experience with networks (even computer cables) somewhere in your past. You'll learn to appreciate subtle aspects of networks you won't get from listening to a lecture. The more varied your experiences are, the more valuable you become as an architect.

[arulk pillai]

It depends on what type of architect you are. For example, .NET architect, solution architect, infrastructure architect, enterprise architect, etc to determine to what level you must have understanding. But a basic understanding of the networks, load balancers, clustering, disaster recovery, sticky versus non-stick sessions, active/active or active/passive configurations, DMZ zone, etc are necessary as you would require to collaborate with other architects and technicians