Not any moreso than learning any other OS. I'd just argue that it's the case if you're averse to research, reading, listening, watching, or just generally learning from others... or if you're delving into unknown territory

Personally, i'm a learn-by-doing type of lady, so I've fucked up my share of devices (I'm allergic to reading unless it's fiction), but I have yet to mess around in the kernel (it's on my todo list, for my LFS build which is TBD)

No no no! When you break something in Linux systems you fix it. Starting over and reinstalling everything is what you do when you mess up on Windows.

It's even better if your only internet connection is that computer you broke.

Pretty much everytime I try to do fancy stuff with the bootloader I get pretty close to nuking systems. Worst was my 1st UEFI system where I was trying to get rEFInd to show multiple OS to boot from... eventually gave up and went back to the warm embrace of GRUB

Nearly always it's been during the live USB install of a dual-boot that a distro messes with the grub or installed grub to the USB disk itself. The fault lies with me because I'm almost blindly trusting the distro, but also with the distro for lacking proper yet succinct documentation during the install or configuration of partitions.

Never the kernel but just about every time I touch /etc/fstab I fuck something up. I've done that a lot....

May I introduce you to my lord and saviour NixOS?

The "starting over" part is what made it take so long for linux to "stick" with me.

Once it became "restore from an earlier image", it was a game changer!

I would actually be amazed if I ever bricked a PC fucking around with installing software to it. At the very worst, I might have to move a jumper pin to flash the CMOS and start fresh like I never even touched the thing. If somehow even that fails, it would be a unique experience.

So, when you say crippled kernel, do you actually mean you tweaked the kernel params/build to the point that it failed to boot? Or do you just mean you messed up some package config to the point that the normal boot sequence didn't get you to a place you knew how to recover from and need to reinstall from scratch?

I think I'm past the point where I need to do a full reinstall to recover from my mistakes. As long as I get a shell, I can usually undo whatever I did. I have btrfs+timeshift also set up, but I've never had to use it.

Uhm, zero? With ten years of using Linux? What did you do to fuck up the damn kernel? o_O

I tried to use dd with too much hubris once. I had to restore from backups (which ironically, I had made with dd). I'm usually overly cautious, but I was in a hurry.

Maybe 1 or 2 back when things were less stable, but any time I have used Linux in the past 7 years or so, and particularly since I started using Debian as my primary OS, I haven't had any problems outside of trying to get some windows applications to emulate correctly, and one time when I echo'd into sources.list with > instead of >>. Anything else is just stuff I had to learn, like my boot folder filling up with old images that have to be cleaned out occasionally.

Another big part is learning how to set it up in a way that it's functional and productive the first time and then STOP FUCKING WITH IT.

I just spent 11 days on a dual boot repair in fstab, passwd, loads of ecryptfs, amongst other boot and login issues. Before restoring from the full system backup after getting mad to finally want to use my PC. 11 fucking days almost all day in terminal. TOO many partitions and too many folders inside of folders to get to my ecryptfs files. I got so lost LSing around.

After it all though, and it was an aneurism and a half. I still want to finish my goal and reinstall my dual boot this time correctly aiming the folders correctly.

OpenSUSE Tumbleweed helps because you can create a btrfs snapshot at any moment and then roll back to it if you get in trouble. And it does this automatically whenever you update the packages.

It's the same as learning anything, really. A big part of learning to draw is making thousands of bad drawings. A big part of learning DIY skills is not being afraid to cut a hole in the wall. Plan to screw up. Take your time, be patient with yourself, and read ahead so none of the potential screw-ups hurt you. Don't be afraid to look foolish, reality is absurd, it's fine.

We give children largess to fail because they have everything to learn. Then, as adults, we don't give ourselves permission to fail. But why should we be any better than children at new things? Many adults have forgotten how fraught the process of learning new skills is and when they fail they get scared and frustrated and quit. That's just how learning feels. Kids cry a lot. Puttering around on a spare computer is an extremely safe way to become reacquainted with that feeling and that will serve you well even if you decide you don't like Linux and never touch it again. Worst case you fucked up an old laptop that was collecting dust. That is way better than cutting a hole in the wall and hitting a pipe.