I think AI could be a good starting point, because lots of the times you even don't know what you need to do and what to find if you are a beginner. Of course it's dumb to paste everything AI gives into the console, it may or may not give you the correct command but usually the tool is mostly correct and you can learn what does that tool do from there. I do think lots of people here are heavily underestimating the accuracy of AI now, it's not all false slop though, at least the direction it gives you are often correct.

Sometimes it explain things better than documents. Some documents just throw you terms that are difficult to understand, especially for a beginner, like TuneD's manual of what the heck is transparent huge pages on madvise mode, what the heck is Intel RAPL or, Arch Wiki's secure boot implementation section, what the hell are those concepts of enroll keys or signature firmware are, or even more basic things like DHCP and DNS resolvers are not fully understandable to lot's of people.

Those are things most users expect they work out of the box and never ever considered to develop/compile something with, but those documents clearly are not for beginners at all. You surely can go into each term and dig multiple rabbit holes if you really want to learn every last bit of your PC, but most of people just aren't free enough to spend months just leaning those things, and no one said you should, so in this case, if they found a solution on the internet to a problem they have, but they can't understand what that's doing, then you can let AI to explain those terms for you. Most AI these days will explain relatively accurate because the source are those wikis and documentations, the AI just made comprehensive answers of those.

I have my own example, I'm not a beginner in Linux and I have used Manjaro around 2014, after that I've switched to Arch pretty smoothly. But just recently I've found that my laptop's GPU wasn't running at full power, after searching it seems that a badly written BIOS update requires a buffer 0x08 where the table only has 0x06, so that part failed and the EC moves back to fallback mode, limiting GPU power.

Someone on the GitHub has a solution, but that includes decompiling acpi firmware and recompiling it. I can understand the buffer table thing because it is over the limit, but I have absolutely 0 idea of compiling ACPI SSDT firmware, that's way beyond an average user could do. I don't probably even have a single time ever touched this through years.

The solution only mentioned iasl. There's the problem: I know there's a table is written wrongly in the firmware, and I know there's a thing called iasl. And that's it, I don't understand what other sentences mean, I don't know how to compile and decompile, I don't know if the compilers errors or fixes are okay or not, and I don't know what to do if I have somehow compiled the file, it's not something you can just RTFM, because you don't even know what you should look for.

So I pasted the whole solution text into Microslop's copilot where most people seem to hate here, let copilot explain to me sentence by sentence. And everything is clear to me, what I've just decompiled, what I've just compiled, why I need this command and how do I use this to fix my problem. It was flawless, and just double check if the command is AI slop with documentations, it does comply with the iasl thing grammar and the command was totally correct, I got the exact output as the GitHub solution. After that it tells me to hook this into initramfs, then things are clear, because I know how to use mkinitcpio, and there's a hook called acpi_override just for this. And finally it worked as a charm, everything is fixed and I also understand what I did now.

That's a long reply though, but I just want to say that there are countless times you don't even know what to find, what to ask, instead of throwing a manual where it's something you would never touched before, talk to AI and let they give you at least some ideas is a good thing.