The way you talk about a recursive function with another engineer is not the way you explain progress to a stakeholder, and it is not the way you talk to a frustrated customer. Same brain. Three audiences. Three jobs.
Your technical work does not travel on its own. If the people around it cannot use it, the work stalls.
Peers: the code review
A review can make the code better or make the author smaller. The difference is usually the language.
The pedant treats the review like a quiz they intend to win. A dozen comments on braces. Silence on the actual design. The author leaves diminished. The change is not safer.
The useful version is curious. "What trade-off were you making here? Does this get expensive under X?" Challenge the idea. Be willing to lose the argument. Point at the clean parts out loud. The person on the other side of the diff invested time. Act like it.
Stakeholders: translate, don't lecture
They do not live in data structures. They live in time, money, and whether the thing helps a customer. Your job in that room is not to prove the work is hard.
The professor version stands at a whiteboard and unloads microservices, Kubernetes, and gateways until the room is lost. Expertise demonstrated. Nothing decided.
The useful version answers "so what?" A migration is not an ETL procedure. It is why the next feature will be cheaper. Technical debt is not a purity issue. It is why the roadmap slipped. Speak in outcomes. That is how you get treated like a partner instead of a cost center.
Customers: diagnose first
A lot of engineers dread this conversation. It is also where the code meets reality.
The prescriber hears a keyword and fires a script. "Clear your cache." Ticket closed. Context ignored. The same person comes back, more angry.
The useful version starts with what happened, in their words. Even if the fix is still "clear the cache," it comes after you understood the pain. You are not only closing a ticket. You are deciding whether they still trust the product.
The common thread is not a personality type. It is whether the other person leaves the conversation with more clarity than they brought in.