If AI Helps You Learn Faster Is It Cheating?
I built a networking reference guide because there was a gap, not in the market, but in my own head. Electricians have Ugly’s Electrical Reference, a beat-up pocket book packed with wire gauges, conduit fill tables, motor formulas, and code notes you can grab fast on a job site. I kept waiting for the networking equivalent: something compact, practical, and written for the moment you are standing in front of a switch and need the answer now. As a broadcast network engineer who came up through audio, video, transmitters, and signal chains, I learned IP networking later and mostly on the job. That creates a special kind of friction: you work next to people who can recall OSPF neighbor states from memory while you are still trying to keep the OSI model straight. When you learn by doing, repetition matters, but the real world does not pause while you search, reread documentation, and fall into rabbit holes.
The pain is not that Google or AI are useless, it’s that they are too wide. Standard network documentation assumes you already know what you’re looking for, so you can navigate to the exact detail. If you struggle with focus, “just look it up” becomes 18 browser tabs, half a YouTube video, a Cisco documentation page you don’t fully understand, then coffee, then you forget what you were even trying to solve. In the middle of troubleshooting at night, maybe chasing dropped packets on an AES67 stream, you do not want three blue links or a long chat response. You want the exact command, the port number, the right Wireshark filter, the subnet math, or a plain-English VLAN explanation you can trust. The core idea is a narrow tool on purpose: a personal networking cheat sheet organized the way your brain navigates, searchable in under a second, and designed to keep you out of adjacent-link chaos.
So I “vibe coded” a locally hosted single-page web app, using AI to do the heavy lifting while I stayed the architect and editor. No logins, no cloud dependencies, just something that runs off a laptop or a local Nginx server, with a dark theme, a sidebar of categories, and fast search. The content is the point: subnet calculators, common port numbers, OSI model in plain English, Cisco IOS commands, config snippets, and quick reference tables. I added practical generators and builders too, like Cisco config generators and Wireshark filter builders, plus broadcast-specific networking references like StudioHub pinouts and PTP IEEE 1588 filters. It is not a comprehensive networking textbook, it is a comprehensive networking reference for my job, built by someone still learning for someone still learning.
The surprising part was that writing prompts forced me to inventory my knowledge gaps. “Add a section about VLANs” produces generic filler, but “Explain VLANs in plain English, include a Cisco IOS config example, and list the most common mistakes” produces something you might actually reach for. That specificity becomes a learning method: you name what you don’t know, define what “useful” looks like, review the output, then edit it until it matches how you think and talk. AI is not the teacher here so much as the power tool. The learning comes from building: seeing the command, using it, seeing it again, and eventually not needing the reference. The app becomes the in-between layer, the training wheels that keep you in the work instead of lost in search results.
There’s also the cultural tension. Some people, including people close to me, are anti-AI and worry that it outsources fundamentals. I get the concern, but this is not a product launch, a SaaS, or a course promising “ten times your networking skills.” It’s a slightly janky personal tool built to bridge the gap between where I am and where I need to be, and it helps me practice with repetition in real scenarios. If that offends someone’s sense of technological purity, they don’t have to use it. But the bigger takeaway stands: if you are actively learning a knowledge domain and the perfect resource doesn’t exist for your brain, you can build it now. Describe what you need, let the machine propose structure, edit relentlessly, and turn your reference into a living record of your learning.
My vibe coding network toolkit.