I started working in IT at 15, but it wasn’t until I turned 16 that I really came to understand what “networking” meant beyond diagrams and certification books. Working for a local tech business that handles everything from managed IT services and cybersecurity to structured cabling and network infrastructure, I got thrown into situations where the network isn’t theoretical; it’s the backbone of a school, a clinic, a government office, or a small business trying to stay afloat.

Nothing accelerates learning like walking into a site where the WiFi is down, switches are unlabeled, and the only documentation is a sticky note that reads, "DO NOT TOUCH."

At 17, I went from learning to truly studying. I wanted to know why things worked as they did. Why does a link flap? Why does a device negotiate at 100 Mbps instead of a gigabit? Why does a packet capture reveal patterns unlike user-reported symptoms? That curiosity pushed me deep into overlooked network layers.

I learned to read the physical layer like a language: signal integrity, duplex mismatches, bad crimps, impedance issues, and the subtle clues NICs give long before a device "officially fails." I began troubleshooting at Layer 2 with intention, not guesswork—spanning tree behavior, ARP anomalies, VLAN misconfigurations, broadcast storms, and the surprises you find when someone connects a switch to itself because "it fit."

Packet analysis became one of my favorite tools, not because it’s glamorous, but because it’s honest. I reach for Wireshark almost daily, since it’s simple and lets me see all the traffic down to each frame and protocol exchange. Logs can lie. Users can misremember. But packets don’t. They tell you precisely what happened, down to the microsecond, if you know how to listen.

And cabling, the part of networking everyone claims is “simple”, became something I genuinely enjoy. There’s an art to building infrastructure that’s clean, reliable, and future‑proof. Good cabling makes networks predictable. Bad cabling makes networks unstable and alive in all the wrong ways.

Over the past few years, I’ve helped design, repair, and optimize networks across schools, healthcare clinics, government offices, small businesses, and residential environments. I’ve learned how to build infrastructure from the ground up and keep systems running for people who depend on them.

But the part that keeps me in this field is the service aspect. Networking isn’t abstract when you’re the one restoring connectivity for a clinic that needs access to patient records or fixing a school’s Wi-Fi so students can actually learn. It’s hands‑on, unpredictable, and it matters because it's meaningful.

I’m still learning, constantly, just like all techs, and that’s the best part. Networking is deep, layered, and endlessly evolving. Whenever I believe I’ve mastered something, I find another corner of the stack worth exploring.

In future posts, I’ll be sharing more about the technical side of what I’ve learned: packet analysis workflows, telemetry insights, L1/L2 troubleshooting strategies, and the occasional field story that every technician can relate to. If you’re into the gritty, practical side of networking, you’ll probably feel right at home.