What I learned when a code-review comment of mine was taken as an order: explain the why, and treat review comments as discussion.

Before presenting a design, list the questions your CTO, teammates and other teams will ask, and answer them first.

Stuck on a bug or feature? Timebox it, take breaks, rubber-duck it or ask a teammate, instead of sitting at your desk until it's solved.

Implemented, reviewed, tested, deployed: the levels of "done" I've seen, and why your team needs a shared definition of done.

Spot classes that solve the same problem differently, extract the common part into a generic pattern, and replace old code step by step.