{"id":110,"date":"2020-03-10T00:06:16","date_gmt":"2020-03-10T07:06:16","guid":{"rendered":"http:\/\/www.markjwicker.com\/?p=110"},"modified":"2020-03-10T00:06:16","modified_gmt":"2020-03-10T07:06:16","slug":"be-more-than-just-a-network-engineer","status":"publish","type":"post","link":"https:\/\/www.markjwicker.com\/?p=110","title":{"rendered":"Be More Than Just a “Network Engineer”\u200b"},"content":{"rendered":"\n
\"\"<\/figure>\n\n\n\n

To all of my Network Engineering folks out there – As you know, we (Network) are generally the first place that our fellow co-workers\/colleagues come to when they have issues. Sometimes their issue is indeed truly a network (layer 2\/3\/4) issue but more often it is not. The best thing that you can do is to become knowledgeable about systems and applications outside of purely “network”. No matter what the issue is, you should be a resource in solving it, rather than pointing blame.<\/p>\n\n\n\n

Solving issues is what we do, no matter if they are truly at the network layer or not. I had an issue recently in which my knowledge of WordPress helped to point the application owner in the correct direction to fix. What came in as a “firewall issue” was actually a WordPress configuration\/database issue. <\/p>\n\n\n\n

I have heard something like this generically said (paraphrased) by some network engineers – “It isn’t a network issue and it is not my problem to fix the application or server”. This saying, though technically correct, is not the right attitude to have. <\/p>\n\n\n\n

By learning about the areas outside of pure networking and being able to help our colleagues with their own issues, we earn a tremendous amount of respect that leads to partnership with other teams and grows beyond just being a “network guy”. You will most certainly benefit and grow from having this attitude. IMO – This is how you truly become a “Senior Network Engineer”. This is what it is all about. Be a part of the solution and not the problem!<\/p>\n","protected":false},"excerpt":{"rendered":"

To all of my Network Engineering folks out there – As you know, we (Network) are generally the first place that our fellow co-workers\/colleagues come to when they have issues. Sometimes their issue is indeed truly a network (layer 2\/3\/4) issue but more often it is not. The best thing that you can do is […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[3],"tags":[],"class_list":["post-110","post","type-post","status-publish","format-standard","hentry","category-my-professional-life","count-0","even alt","author-mwicker","last"],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/www.markjwicker.com\/index.php?rest_route=\/wp\/v2\/posts\/110","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.markjwicker.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.markjwicker.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.markjwicker.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.markjwicker.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=110"}],"version-history":[{"count":0,"href":"https:\/\/www.markjwicker.com\/index.php?rest_route=\/wp\/v2\/posts\/110\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.markjwicker.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=110"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.markjwicker.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=110"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.markjwicker.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=110"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}