The part nobody teaches

Technical skill gets you hired. How you work with people decides what you get to work on after that.

Asking well

bad:  "it doesn't work"
good: "The upload fails with a 413 for files over 2MB. I checked the nginx
       client_max_body_size, it is 10M. I think it might be the app server
       limit but I cannot find where it is set. Have you seen this?"

The second shows what you tried, narrows the question, and can be answered in thirty seconds. The first requires a conversation to even begin.

And ask sooner than feels comfortable. An hour stuck with nothing to show is the point, decided in advance so you are not negotiating with yourself at the time.

Receiving review

Comments are about the code. That sounds obvious and is worth repeating, because everyone's first instinct is to defend.

If a reviewer misunderstood something, that is information: the code was unclear to a competent reader, which is worth fixing even when the logic is right. If you disagree, say why with a reason. If it goes two rounds, talk instead of typing.

Giving review

Ask rather than instruct. Distinguish blocking comments from preferences. Say what is good, not only what is wrong. Review promptly, because a pull request sitting for two days is a branch getting further out of date and a colleague blocked.

Disagreeing

State your reasoning and what would change your mind. "I think we should use Postgres because we need ad hoc queries; if reporting moves to a separate system, the argument changes."

Then, when the decision goes the other way, commit to it. Disagree and commit is a real skill, and relitigating a settled decision every week costs more than either option would have.

Saying no, and saying when

"Can you add this by Friday?" has three honest answers: yes, no, and yes if something else moves. The third is usually the true one and is the one people avoid giving.

Over committing to be helpful produces missed dates, which damages trust more than the original no would have.

Visibility

Work nobody knows about is work nobody credits. This is not self promotion; it is keeping the people who depend on you informed.

A short update when something ships, a note when you are blocked, a heads up when an estimate has moved. It takes a minute and it is most of what "communicates well" means on a performance review.