1. Use a issue tracker to report issues. If a ticket doesn't exist, create it.
2. Stick to the facts: what happened, and what should have happened instead? Remove all the noise such as blame, emotional reactions, etc. Less drama, more clarity.
3. If the root cause is something dumb such as the hotel WiFi, close the ticket as "can't reproduce" and add an explanation.
You can avoid reading the text, then use a LLM prompt such as: "Can you rephrase this removing all emotional reactions and extracting only the parts that relate to reproduction steps".
Do not waste energy on toxic people. You are not a therapist, an emotional support animal, a sandbag or a doormat. You are a software engineer.
Unless you are getting rich you should avoid working there.
Hmm, that is an interesting idea. I bet someone could write an app that rephrased incoming messages through an LLM to match some metric you chose. You'd definitely need the ability to read the original message and there's about a million and a half ways out could go wrong but it's interesting nonetheless. Just evaporate toxicity from all communications before they even reach your brain.
2. Stick to the facts: what happened, and what should have happened instead? Remove all the noise such as blame, emotional reactions, etc. Less drama, more clarity.
3. If the root cause is something dumb such as the hotel WiFi, close the ticket as "can't reproduce" and add an explanation.
You can avoid reading the text, then use a LLM prompt such as: "Can you rephrase this removing all emotional reactions and extracting only the parts that relate to reproduction steps".
Do not waste energy on toxic people. You are not a therapist, an emotional support animal, a sandbag or a doormat. You are a software engineer.
Unless you are getting rich you should avoid working there.