Presently unable to find a post that I'm sure I've seen reposted a few times on here, but I'll summarize the final point because it's what started this whole train of thought. "If someone is mad at themselves [for being unable to do something with their computer], redirect it. It's the computer's fault for being designed badly." The software is broken. The user experience isn't as smart as it needs to be.
Helping people learn how to do things with their computer means having to redirect a lot of that frustration. It is an exercise for the very patient; the helper must have enough patience for both themselves and for the customer. (I am using "customer" here, even though this applies just as well to hobbyist work for which no money is exchanged. I find the attitudes are the same regardless.) There is a lot of generic rote that needs to get taken into account, and it will be frustrating or annoying to a lot of users, but it's rote for a reason. The guy having performance problems on your game from his Gaming Laptop will, at some point, need to tell you that he is on a Gaming Laptop to begin with. And getting that information out of them - while they're already stressed or upset about the thing Not Working - likely requires a gentler approach, or some way to talk them down from their mood of anger or despair.
The actual approach, of course, varies by the customer, and knowing a thing or two about psychoanalysis (hello, Psych degree-havers and/or armchair psychiatrists!) definitely helps here. But what also helps is empathy. Maybe not get into their head, but at least understand where they're at mentally, emotionally, maybe even spiritually. Help them to understand that they're not alone, that this can be solved and that you (and anybody else present) are there to guide them to getting it solved.
So often I see approaches to tech support that just leave me scratching my head. Corporate tech support, like the kind with call centers, is so focused on getting the problem solved fast that they've got it down to a script; a script that often is designed for the most common problems first, and ends up patronizing the customer. The longer the customer has to put up with "and are you sure you restarted your computer just now?", the more upset they'll be. This probably isn't a thing that can be remedied, for as long as corporate tech support centers around success metrics over solving difficult problems.
On the other end, hobbyist tech support - of the "message the author or join this chat" variety - often feels like, to the amateur supporter, more of a mouthpiece to push their own use case. When presented with a problem, a Joe Random user - it doesn't even have to be anybody related to the project - can frequently fall into one of two "solutions" to a problem that they personally have not experienced. The first is the "oh, well, it works for me" comment, made from a lack of any critical thinking or attempt at investigating. The second is the "just switch!" user, who'll advise the complainant to try another OS. I've complained quite a lot about that over the years, but to summarize, you do not know this person's entire use case for their setup. Abandoning Windows for Linux or macOS (or BSD or QNX or OS/2 Warp or Plan 9) might get rid of the initial problem, but it is going to create several other problems in the form of the learning curve. It is going to detach the complainant from a lot of the things they were needing to do outside of whatever was broken before.
...This post has been in my drafts for over a year. I don't even know what my central point was going to be, anymore, but maybe these thoughts will be of use to somebody. Time to let it out.