This is admittedly a bit pedantic but it’s not that the risk doesn’t exist (there may be quite a lot to gain from having your info). It’s because the risk is quite low and the benefit is worth the favorable gamble. Not dissimilar to discussing deeply personal health details with medical professionals. Help begins with trust.

There’s an implicit trust (and often an explicit and enforceable legal agreement in professional contexts (trust, but verify)) between sys admins and troubleshooters. Good admins want quiet happy systems and good devs want to squash bugs. If the dev also dons a black hat occasionally they’d be idiotic to shit where they eat. Not many idiots are part of teams that build things lots of people use.

edit: ope replied to the wrong comment

deleted by creator

Start here: https://nesslabs.com/how-to-think-better This isn’t an endorsement (though I do like ness labs). That article offers practical evidence-based starting points and additional resources at the end.

There are many people/systems/schools that will offer strategies and solutions. Some are practical and effective. None of them are a replacement for learning what it means to think well, learning how to think well, or actually thinking well.

The next step is learning the jargon of philosophy so you can ask meaningful questions and parse the answers (this is true for any new discipline). I recommend reading anything on the topics of epistemology, ethics, and aesthetics, which resonate with you. Then find others to discuss what you’ve read. You do not have to be right or knowledgeable to earn a voice in the conversation: only an interest in discovering how you might be wrong and helping others discern the same for themselves.

If you haven’t read any classical philosophy but are interested I recommend Euthyphro. It’s brief, poignant, and entertaining.

I hope this helps! Happy to discuss further as well.