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.

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.

Working for a VoIP company in the early 2010s I rm -rf’d the /bin/ directory. As root. On a production server. On site.

I ended up booting from my phone (android app for iso booting) then manually coppied over the files from another machine. Chrooted and some stuff was broken but rebuilding from the package manager reinstalled everything that was missing. Got the system back up in around 40 mins after that colossal screw up. Good fun and a great learning experience. Honestly, my manager should not have had me doing anything on a root shell with no training.

For the software side I would recommend Linux Mint as a great simple starter distro with good support and a nice community. The overall design paradigm is about maintaining familiarity while also making sane defaults and simplifying processes. Because it is Ubuntu based it is also easy to get documentation and support because what works for Ubuntu also works for Mint.

For hardware it really depends on your budget and locality as well as use case. Laptops vary much more country to country than you may think, so it may be worth thinking about what is local to you. For example, I live in Australia so System76 is a bad choice here, same with SlimBook (I think that is the name, European KDE laptop that advertises with that French(?) YouTuber, they don’t ship here.

Also, when looking at laptops the RAM configuration is important. If you have two RAM slots but only one RAM stick you will have really slow memory access. This will bottleneck for both the CPU and GPU if you are using both at the same time, say during gaming or doing AI work. Swapping out the single stick for a matching pair or just adding one more stick that matches what it already has will let both ports work together, making everything faster. Also when I say matching I mean in terms of size and speed. If you put 3200MHz and 2400MHz in the system at the same time the 3200MHz won’t just down tune to match, they will both go slower as far as I am aware. Best to match not only the speed but if possible the brand and ideally model, there are lots of little differences between RAM sticks and honestly it has never been worth the trouble in my experience to have mismatched sticks, I just replace with a matching pair.

It looks like it is downsampling the video or streaming after converting to another codec. Some codecs are fine for decoding on the server but the app may not support them so the server converts them. Some files are of higher quality than what the server is configured to deliver so it downsamples to stream it.

Check the configuration and look for anything to do with codecs, hardware decoding, streaming quality, and so on. It may also be on the app, so if you can access a different interface then test that to narrow down the issue.

Something I have found is missing from both of these suggestions as well as every podcast app on device is transcoding to speed up so it is not sped up on the fly. For a lot of phones and other devices the task of playing back at 2x speed is enough to demand a higher power state than what is required to play a sped up file. For efficiency doing a single pass of speeding up the audio then playing back at that speed would use less power during the playback phase, allowing you to download and speed up all of your podcasts at home while on charge then listen for long periods without completely killing the battery. I have checked with a few if the open source devs and this is not a feature they see utility for so nobody intends to make it.