My personal background in computing (specifically networking) is atypical. I have a bachelors in visual arts and only took a handful of computing classes in my relatively long tenure in college. However, I did learn one valuable lesson that has served me pretty well over the 15 or so years I have been doing networking and I’d bet money any good network engineer that has more than 10 years of experience will nod their head at this and agree. A really good Network Engineer knows enough about any discipline to successfully function in that role. A network engineer is the “grout” of nearly every place I have ever worked. They fill in all the gaps left behind by departures, lack of funding or just general need. It takes a certain kind of personality to be a good one and when you find a good one, you should keep them, they’re hard to come by. As an example, in the course of my career, it has been necessary for me to: 1. Be a UNIX and Linux sysadmin. This includes such things as:
a. being a mail server admin
b. maintaining web servers
c. running monitoring systems
d. administrating virtual machine hosts (and guests)
e. creating, managing, troubleshooting and upgrading DNS and DHCP servers
2. Function as a network security policy writer
3. Act in a desktop support role 4. Modify, debug and create code. 5. Work as a windows server admin 6. Perform as a network security engineer (evaluate, install, debug and maintain firewall, IDS, IPS and VPN devices and platforms) 7. Install, test and debug physical infrastructure such as inside and outside plant fiber and copper. 8. Act as a facility coordinator for power, heat and cooling 9. Test, evaluate and maintain phone systems, PBX, CentrEx and VoIP 10. Aid in the creation of grant proposals 11. Present as a subject matter expert to internal and public audiences 12. Operate as a trusted source of knowledge on nearly everything IT related (and if we don’t know, we find out). 13. Oh yeah, keep the network running by having intimate knowledge of networking equipment like routers, switches, customer provisioning gear, DWDM equipment and the interfaces and protocols that make them work. That is just scratching the surface…..and I absolutely love what I do. The packet pushers said it well. “Too much networking would never be enough”. For all of the up and coming network engineers [and the seasoned veterans, too], I offer this bit of unsolicited advice: Don’t be a Luddite. Love what you do. In IT the only constant is change. Embrace it. Learn new technology. Think outside of the box and step outside of your comfort zone. Never be comfortable with “good enough”. Strive to know more about whatever it is you are working on. Be positive. Help others learn. Don’t worry about credit and recognition and just do great work, if you do the rest will work itself out. This post is my ode to the network engineer. On Network Engineer appreciation day (which should be a thing. if it doesn’t exist, I decree it is every November 12th), think of these things and remember that even if no one remembers network engineer appreciation day, we’ll still keep the packets moving and fill in the rest of the gaps too. Cheers.