By: Kevin Gray
You don’t truly know networking until you grok it. http://catb.org/jargon/html/G/grok.html At the architecture level, I deal with the “whys” every day and leave many of the “hows” to engineering.
View ArticleClik here to view.
By: Brannen
Agree with knowing why. I phrase it to my boss as, “I don’t mind being told know, but I appreciate being told why so I understand.” And “Wrath of Kahn” is absolutely the best Star Trek TOS movie.
View ArticleBy: Brannen
don’t know if that was a freudian slip, or an auto correct. “I don’t mind being told no, but ….”
View ArticleBy: Nobody Cares | The Networking Nerd
[…] Cisco trunking? I just fired that off as a way to keep it straight in my head. Or how about my post about a throwaway line in a Star Trek movie that exploded on Reddit? I never dreamed that...
View ArticleBy: Q And A Should Include The E | The Networking Nerd
[…] IT world needs more explanation. We need to know why things work the way they do instead of just getting a response of a few words. The explanation has the keys to understanding […]
View ArticleBy: dnedrow2016
Nice. I’m a software developer and use this quote all the time. Good examples are Swift optionals. If you don’t understand why they work, your implementation is a shot in the dark. Also, when people...
View ArticleBy: Backing Up the Dump Truck | The Networking Nerd
[…] buy dumps. You’re not doing yourself any favors. Learn the material. Learn the process. Learn why things work. When you do this you learn how to handle situations and all their permutations. You...
View ArticleBy: John
Well said. This can apply to many things in life, especially in the computing world. I found myself looking for this quote today after encountering someone who had no idea how to debug a model that...
View Article
