You may want to research emotional intelligence. There’s lots of methods you can try but they are not quick to explain. Some examples.
Ask to explain, clarify. Someone made a derogatory comment - call it out. E.g. What do you mean by X? Are you implying that Y?
Dont get angry. Provide clear incentive to act. Increase the cost of failure. Can be as simple as CC relevant person in the email. State clearly what are the expected outcomes. Highlight the risk. Make sure others know what’s going on.
Question real reason for the criticism. Is it really something in your control? Ask what they would do in such scenario. Dig into details. Point out gaps
Above all stay calm. The more the other person gets angry and confrontational while you stay calm and professional the better you look in eyes of everyone else. It makes it obvious to others who is the big baby and who can the handle pressure.
I don’t know if that’s obvious for people entering this profession but mind that you don’t read code like a book. Check how the functions you use are implemented. What’s being called from where (call stack helps in the debugger). How are experience programmers managing their code etc. It’s a good skill to learn how to navigate other people code and quickly find the parts that matter
Point 1 is pure speculation. You could say the same about any profession. Absolutely not something woth considering when looking for career opportunities. You can always pivot with your career and knowing how to code is a plus because that makes you understand tech better
You may want to research emotional intelligence. There’s lots of methods you can try but they are not quick to explain. Some examples.
Above all stay calm. The more the other person gets angry and confrontational while you stay calm and professional the better you look in eyes of everyone else. It makes it obvious to others who is the big baby and who can the handle pressure.