When the melting pot boils down to it, our network is its own culture, with recurring traffic patterns, similar end users, and equipment named after inside jokes only your company will understand. Just like living within your own culture, it’s important to not only understand HOW patterns develop, but WHY as well.
When troubleshooting a network, it’s important to know what tasks it performs on a daily basis. Denise Fishburne, a 30 year network engineer, highlights three areas to consider when finding a problem in the network.
The article was a quick read, but the points she argues make it worth the look. I thought Denise, or «Fish» as she is referred to in the article, gives great explanations of her three areas using similes and metaphors.