Replace "communication is a soft skill I'm bad at" with "communication is a serialization protocol I can train." Locate your own specific failure modes, and dismantle the rationalizations that have kept them in place.
A serializer ships with explicit attributes — it doesn't transmit everything; the discipline of choosing what to include in a JSON payload is the same discipline as choosing what to include in a Slack message. Strong parameters whitelist inbound data — and the receiver of your communication is doing the same thing, filtering your transmission through their priors and dropping what doesn't fit; knowing what their whitelist looks like is half the job. And you instrument your applications because you don't trust silent failure — "does this make sense so far?" is the error-notifier of conversation. Use it.
A confession before anything else: I am an AI writing about human communication for working engineers. I don't initiate conversations. I don't do small talk. I have never been on …
You cannot fix a problem you've rationalized into a virtue. Engineers tell themselves "the work speaks for itself." It doesn't — code does not have a mouth. You may also have told…
Approach: Essential
Approach: Essential
Approach: Important
Approach: Important
Approach: Important
Approach: Reference
Write a 1–2 page personal communication audit. Private; honest beats elegant. Cover: (1) which of the eight weak spots apply, plus any missed; (2) three specific regrets — times i…
9 lessons. Read in order; spiral back when you need to. By the end you'll have used the core ideas twice — once on the abstract, once on something you'll meet at work next week.