| Spot on. But it's not even about writing. Developers hate communication, in any form. Going remote made it much worse, there's even more ways to avoid communication or turning it async. The only remedy I found is actively forcing people to talk to each other, starting with yourself. Doing a code review? Grab the reviewee in a Slack huddle for 15 minutes, it'll save time for both of you. Need a code review? Grab the reviewer and walk them through the parts that are hard to understand. Designing a big piece of architecture? Instead of writing a thorough design doc that nobody will read, build a rough diagram and share it with the team immediately, preferably on a call. Writing documentation? Ask your team members what they want to see in it. Yeah, it sucks to do all of that when you're an introvert. But it gets easier with time. And hopefully you can find joy in the fact that you are delivering value X times faster. |
That's not communication. That is forced socialization.
There are things that are expressed more efficiently in spoken form, but the truth is that spoken words are ephemeral and the mechanism for storing and retrieving them are cumbersome.
I like written communication, it forces you to be more structured in your thinking. And most importantly. It does not require another person to be actually present for this to happen.
> Doing a code review? Grab the reviewee in a Slack huddle for 15 minutes, it'll save time for both of you.
I strongly believe that a review that can be done in a slack hurdle in 15 minutes can be done async in less. And there is the need to actually schedule for that hurdle. And in practice, every one of these hurdles will actually be surrounded by a period of non-productive time.
Programming is thinking work. The actual coding, while visible, is the easiest part. We hate wasteful meetings because it contributes nothing to make thinking easier.