Been using arch as my first and only *nix for about 4 years now, most of the pain points have been smoothed out, usually you can find answers by searching whatever errors you see or checking dmesg. If you're a CS person, it really isn't hard to solve most issues and reason about, it's just normal debugging / docs / forums. In the event that you're doing something weird and niche, or you really cant find your info, you might reach out to the community and it's likely some linux wizard will solve your issue, like this post.

I was much more frustrated on windows when i ran into issues and your best bet was some incompetent support, and watching blue screens til you come to the conclusion that your system is scrapped, who knows why, and you need to reinstall and start over from scratch.

On arch you can save your dotfiles, make snapshots, chroot to fix things, and so on, there's tons of safeguards you can put in place, and tons of options for remediation. You really just need to RTM.

On top of that if you have a gripe about some software not working how you think it should, you can usually hack it or replace it. If you have an idea for some new functionality you want you can usually find/install some existing software for your needs in like 2 seconds, or you can find the repo of your software and submit an issue or PR.

Alternatively you can also just string together existing tools in a script in order to fulfill your needs. I did this recently to create an OCR screenshot to clipboard tool using tesseract and flameshot, something I wouldn't have even considered possible on windows.