I am aware like we all are, that around 1/20 of the salary bill at a software company go to those in test and support roles. Sorry, but this is no surprise, but if we do use real world events more often as a narrative, about what we do, then it suddenly makes more sense to readers. For example when 29 people died in one totally out of the blue crash back in 1994, everyone blamed it on the people, and it ruined peoples lives. It took a decade to even suspect in the minds of more than a few people, probably all technophiles, that the accident was a computer software error. And it ruined 2 families lives, destroyed them with the blame cuslture humans seem to enjoy, until the truth was found. Read more here Chinook helicopter disaster - computer software failure or pilot error?
So yes, we do need to put the real world into our software world, and put that world into our testing world. I love trying to badly draw parallels between things, like when my kettle or toaster stops working, and my job as a software tester. But I completely agree with @hylke , we need to cover wider ground.
I’m also completely aware of “clubism”, been journeying on MOT for a while now, and as a very bad people reader, I never noticed the little gangs in the test industry until I noticed people leaving the clubs and the industry. This does mean i get into arguments with people in twitter too, because I have to disagree with my world, in order to know that it is solid and real. I’d like to think that as testers, we take our “club” (I mean being a tester, not the MOT club) seriously, and realize that as testers we are all working together to do amazing things such as enable self driving cars, moon landings, and much more. It does sometimes distort our own perspective, and one hopes we as testers have heuristics by now to alert us to this kind of distortion. On one level even your faith or none, is a system of tests. As usual, test everything, and keep the good.