A great technique that a manager set me on the path towards, and that I learned over the last years is to ask many good questions. this takes practice. a good question pushes the other person towards an insight, but lets them supply their own experiences and gives them the satisfaction of figuring something out vs. being told what to do.
For example, instead of stating "this container needs a readiness probe", you could ask "what would a good readiness probe be for this container?", or even more open "how can we make sure this gets taken out of traffic when it breaks? how can we detect that it's broken?"
I found the questioning approaches from Resilience Engineering/LFI helpful, especially to never ask why – it's always an accusation. Better questions are How and What. Sometimes it takes me a few iterations in my head to go from "Why" to "What benefits" (why in a cloak) to some other, much more tailored and thus more useful question about the concrete thing.
It can be useful to prefix the question with some information that the other side doesn't have: "Kubernetes has readiness probes to take bad pods out of service. Under what circumstances would we want that to happen?"
Adjust this to the situation – in some cases, the questions need to be way more broad than in others. This depends on context, how quickly a decision is needed or desired, the knowledge base and needs of the other person. It's not super helpful to be Socratic in a code review when you want concrete changes ("How could we format this line better?" when you really want them to run the autoformatter).
Over time, this will take you from being the grumpy person with lots of opinions, to being the wise one who always asks the helpful questions. It lets others grow, because you guide them on a journey of discovery. It leaves the door open for answers and solutions that you weren't expecting. And it gives the others a warm fuzzy feeling 😄