Well, you may or may not like reading this, but here goes... > I've been in this field a long time, and I cannot think of a single topic which would be better

Well, you may or may not like reading this, but here goes... > I've been in this field a long time, and I cannot think of a single topic which would be better served by video, than reading text. Video takes more time, has more cruft, such as blah blah I made this video because, and I discovered this because...), and video poorly presents for work involving typing. Ironically, the opposite is why I resorted to the videos. The text was often wrong, or useless due to being for some outdated version that doesn't apply anymore for some reason. A good example of this is text code snippets that use hypens when Arch expects an underscore. Which brings me to this... > But videos? How do you copy/paste code snippets from a youtube video? Or go through a list of 7 files to edit and look at? I type it out. I don't copy and paste unless I trust the code I am looking at. And I only trust things as far as I can throw them... Or know them. So yeah, I write it all out, myself. And so I remember it better that way for the future. > Are you watching these videos, then making notes? Text instructions are the notes! More like I write it out in terminal to see if it works and does what I want, then (and I only recently started doing this part) I write down that code for my own use in a notebook for later. Which yes, I still type out. Why? Because copy and paste is useful, but also lazy. IMHO. And quite frankly, I think this is part and parcel as to why things are becoming gibberish and utterly useless. The code being shared is either wrong, mistyped, or just missing things entirely. Arch wiki as I said before, I really should just deep dive into; but it was written by (IMHO) blowhard elites who only wanted people who already knew BASH intricately before installing Arch. On some level, I don't blame them. I agree with the idea of barriers of entry to some certain things. But that thing is a whole new level of bullshit. Bullshit that I was able to get past and beyond, by just following a few videos where each person added in what the other left out. I tell ya. The locales file was a pain in the ass for a while until I found the RIGHT way to do it. (Which I forgot again, but that video is still up, so I can thankfully refer to it) Long story short, each tutorial text/video basically has a person changing it, when really... if you live in Canada or USA, you probably don't need to touch it much or at all. Same goes with the timezones, etc. Only small things need to be done to them. But some of these tutorials just give ya the work around until you bork your installation and have to start over again, wondering what went wrong. So, with all due respect; I do not agree that following the text is the best method. Videos at least show you that the system works for them, even if they left something out. Which means you just need to find what they left out. And I'm great at doing that sort of thing. In the meantime, when I do my next install of Arch, I'll be writing down every little thing this time in my new little notepad, so I have a proper script to follow for any device I come across which has all AMD parts. Then I'll do the same with my laptop that has Nvidia in it... which means dealing with that bloody F'ing gpu switch stuff between integrated and dedicated graphics. Then I won't need to refer to much else than the Arch Wiki for the few things where it matters. Or some random blog where the information is actually legitimate. Like the BTRFS blog I came across that helped fix the suddenly filling SSD issue I ran into the first time I decided to leave EXT4 in the past where it belongs. (so many borked file systems because of a power outage because of that tripe.) And I realize this may all seem wrong to you, but remember... It works on my machine. So that's all that matters. Once I have this finally mastered as much as I care to master it; I'm moving on to Gentoo.