That’s a great list! One thing I would add is empathy. There seem to be a lot of great engineers who are also strong communicators, but still struggle with this.
For example, if someone encounters a problem when running or integrating code you’ve written, you will almost always get to the heart of the problem more efficiently and with less negative emotion if you start by demonstrating that you empathize with that person’s frustration. That’s true even if the issue ends up being something on their side of the line. Acting defensive in these situations is natural, especially if you feel that anger is being directed at you unfairly, but it tends to just get in the way of finding a solution.
Absolutely. It's incredibly easy to be a condescending engineer, thus sabotaging yourself and your ideas. Practicing empathy is a tremendous benefit to yourself and your team!
In my opinion anyone who does not have verifiable proof for their technical competency is not worth the time listening to their talk. I am not saying they don't have valid points but its too much of an ask.
For example, if someone encounters a problem when running or integrating code you’ve written, you will almost always get to the heart of the problem more efficiently and with less negative emotion if you start by demonstrating that you empathize with that person’s frustration. That’s true even if the issue ends up being something on their side of the line. Acting defensive in these situations is natural, especially if you feel that anger is being directed at you unfairly, but it tends to just get in the way of finding a solution.