I recently rewatched an episode of The Art of Network Engineering where hosts Andy Lapteff and William Collins interviewed Muna Chimso about his dual experience in networking and programming. In their conversation, Andy asked a thought-provoking question:
"Why doesn't anybody want to go into networking?"
It's a valid question. I have met people who struggle with networking, but that's not the point. Many are drawn to other fields: cybersecurity, programming, AI & machine learning, the cloud ... the list goes on. I reflected on the question for myself. What drew me to networking? Here are my 5 answers. Maybe you can relate.
1. Networking is everywhere
Everything relies on a network. Think about it: our smartphones, operating systems, and driverless cars all rely on a network for communication. Because it is so pervasive, understanding networking can make troubleshooting quicker and easier. Improving your home network can be exciting. Building home labs prepares you for what you would encounter in a production environment, which is what companies and users rely on.
2. Understanding networking is fundamental
When you think of "networking", what comes to your mind? The term may evoke maintenance windows, DNS issues, Wi-Fi, or a laggy videoconference interview while at home. You may also think of switches, cabling, and massive server rooms. Even so, traditional networking has a place in developing the fundamentals of cybersecurity, machine learning, cloud computing, and modern networking architectures, such as SD-WAN. It serves as a foundation to develop critical IT skills in many domains.
3. It's an overlooked field
According to the Bureau of Labor Statistics, the 10-year job outlook for computer and information technology occupations shows growth in different fields:
Occupation
Projection
Information Security Analysts
33%
Computer and Research Scientists
26%
Software Developers, QA Analysts, and Testers
17%
Network Architects
13%
Computer System Analysts
11%
Database Administrators and Architects
9%
Web Developers and Digital Designers
8%
Computer Support Specialists
6%
Network and Computer System Administrators
-3%
Computer Programmers
-10%
Network architects have a solid 13% growth projection in the next decade. Popular fields, such as cybersecurity and software development, are expected to continue to have an industry boom. This is still good. We need to secure our infrastructure and design user-friendly infrastructure.
However, it reveals an important truth - there's a need to manage, monitor, and configure network and computer systems. Even with a projected decline within the next decade, there will be a need to build efficient, scalable networks for neural networks that build our AI systems. For example, the best models will require high-performance metrics, such as low latency, high throughput, and efficient transfer of heavy workloads across different media, such as Ethernet and fiber, and high-performance interconnect architecture like InfiniBand and RoCE (RDMA over Converged Ethernet).
High performance interconnect architecture allows for fast, efficient transfer of heavy data workloads between systems within computing environments, such as data centers, quantum computing labs, and AI clusters. Standards, such as InfiniBand and RoCE, enable low-latency connections and high throughput between GPUs, storage networks, and networking architecture, like switches and routers.
In the episode, they also mentioned the lack of abundant opportunities for networking. Whether it is the job title or shifting focus, networking is an underrated field that keeps our systems running.
4. I explored around IT and networking just clicked
These points may start to get personal, but the focus is less on the what and more on the how. Networking interested me because of the steps I took. My IT journey started at my community college. Being new to the scene, I explored data science. I was also interested in electrical engineering at the time. Eventually, I changed direction because it would take too long for me to finish my degree. I was aiming for a four-year degree while saving the most money and getting what I need to know. I started to think: which field is similar to sending electrical signals through conduits? The answer was networking!
As I continued toward my AA degree, I started to look for jobs. I lacked the knowledge and expertise. After doing research and examining endless job descriptions, certifications kept appearing as requirements or preferred.
I started with CompTIA A+ since it is a solid entry-level certification (and jobs asked for it). At one point, I was tempted to skip and do Network+. However, I recognized many of the topics discussed are explained in A+. It helped fill in knowledge gaps that would have been gaping if I went straight to Network+. I consistently scored high in the networking domain on practice tests. This only built my desire to go into networking.
5. It is how I started into IT
I like to consider this as where I truly began. The more I continued into networking in my free time, in my studies, and in certification prep, I grew more engaged. I started to wish I knew how to get into my wireless AP and change configurations. I wanted to build a home lab.
Then, I transferred to continue in my studies to get my bachelor's in information technology. My classes were more concentrated and built my skills: virtualization, networking, cybersecurity, and some programming. These classes have led me to develop a well-rounded understanding and applicable skills.
Overcoming Networking Roadblocks
Back to Andy's question: Why doesn't anybody want to go into networking? If you have experienced this in your work, when just starting, or having second thoughts as to your current path, do any of these resonate with you?
There's too much theory
There's too much change
Costly due to certifications
Doesn't offer much room for creativity
It's not being taught as much or focused on much as it should
Low salaries
Fear of bringing the network to its knees
Never even thought of it
If you relate to any of these, you're not alone. These, along with many others, are valid concerns many people have shared. The question is - what can be done? Here are some tips:
Embrace what you don't know and do research. We never truly know everything. That's okay. That is why we have Google, RFCs, and other documentation. Seek to learn from fellow colleagues or others in the field.
Find a networking niche. Networking is broad: automation, wired, wireless, design. Currently, I am working with radio communications, which is a medium used in wireless communication.
Create your home lab. Whether it is virtual or physical, home labs prepare you for a production environment. If you mess up here, it's all good. In this field, troubleshooting and monitoring are good skills to have.
Listen to podcasts and get new insights. I have really grown an interest in networking due to podcasts, videos, and readings. Podcasts provide a real-world analysis for someone like me may not experience much of in their daily life. Yet, it can make you wonder how you can prepare.
Join a networking study group, conference, or committee. Communities and study groups Reddit, Discord, Slack are all great platforms for learning and helping others.
Go at your pace. In my preparation, I personally find I do better if I study on my own. Why? I can do research at my own pace. Focusing on understanding can help you in the long run.
So what's next?
This is different from the posts I have done, less theory and more real talk. The goal of this blog is to humanize our networks. Put it more in the spotlight. With the current state of technology, we are never truly ahead. There is always a new discovery, opinion, protocol, or technology.
Change can be intimidating. To overcome that, I have seen the benefit of having intrinsic motivation to continue. Pursue my main goals, learn more, and be willing to help when needed. In the end, it is about finding what helps you make ends meet and to do so while enjoying it. Find your why (it's cliche, but true).
Have you related to any of these? If so, share your story in the comments. Let's put a face to our networks.
Whether it is a to-do list or a big project, organization is key. We have busy lives. The task in itself can have several parts or may require some sort of collaboration with a partner or a team. A project may call to meet deadlines, which means keeping up with those crucial dates and having a system of order. Similarly, our networks are busy, transferring a great deal of data across links and nodes. The amount of traffic generated can lead to bottlenecks, packet loss, and delays. A network’s design can vary in complexity, depending on the environment or needs of a customer. Just as we find a manageable way to handle heavy workloads, our networks have a way of efficiently handling network traffic by creating "mini-networks" within our network. This process is called subnetting. Why We Subnet To reduce congestion. Just as traffic in cities cause slowdowns and delays, too much traffic can lead to bottlenecks, packet loss, and delays. Subnetting breaks the netwo...
Lab time! Want to build a DHCP server? In this lab, I will show you how to build your own DHCP server on a router using Cisco Packet Tracer, as shown above. By the end of this post, you will be able to create your own DHCP server with a Cisco 2911 router, perhaps in a home lab setting, and prepare you to build your own on other hardware. Why a Router? A DHCP server is a centralized, automated service that assigns important network configuration details to devices on a network, such as IP addresses. Without it, we would have to create manual entries for our entire network, which can be time-consuming and lead to errors. Traditionally, there are dedicated servers to handle these functions. There are many ways to implement a DHCP server in your topology, including a dedicated physical server, a virtual machine, cloud-based gateways, and firewalls. However, there are specific benefits to using a router as your DHCP server: Reduced infrastructur...
Networking is ... Let me hold off on that. Expect a definition later. First, let's set the scene. This is a new platform, new field, new everything for me. You might or might not ask yourself - how? If you are part of the "might not", I get it. I am currently a college student just trying to make sense at staring at the daunting Mount Net - one of many peaks among the IT Mountain Range that grows not centimeters every year, but centimeters every second it seems like. Yet this is a trek I know I want to take step by step. Let me just say, my journey to networking started a few years ago. When I graduated high school, I had different interests - psychology, math, animal science, just to name a few. I had a brief stint of interest in electrical engineering that sparked from a fascination with electricity. My mother also told me that my grandfather used to be in ...
Comments
Post a Comment