My understanding is you make fewer but more replicable mistakes. If you use a wire you have to trace it, keep the length consistent for timing reasons, use very consistent soldering technique, and ultimately you have a hard time tracing issues. With a homemade PCB you generally do get what you ask for in terms of circuitry. Traces are the right length, right thickness, right spacing, and if not then the whole board is similarly impacted, so it is obviously broken or not broken. If you mess up your design then you have a problem, but if you did the process right and you have a valid design then it works.
That all said, homemade PCB is a large time sink and modern PCB manufacture is so cheap and fast it doesn’t make sense to do at home for the most part. You can literally get a complex board faster by ordering it from halfway around the world and having it posted than making it yourself. I would say it is a good learning exercise, not a good manufacturing or prototyping practice.
I don’t know about videos but having a look at the OSI model is a good way to start. It covers the abstract framework for packetizing data including things like the distinction between hardware and software, envelope, encryption, application layer stuff, the whole shebang. The cool thing is by going hardware, network, application you can see where responsibility are and it helps you understand where things can go wrong.
If you are interested there are plenty of CCNA style courses available on the internet, licit and otherwise, and they go into more depth, and the same applies to RHCE/RHCSA material. The training for certifications like that covers what you want to know but also puts it in context, and again licit and otherwise sources are available.