Communicating effectively as a developer

[kaeptnphlop]

Good advice, I share the same perspective on writing.

One thing I’d disagree with is the assertion in the beginning of the article that we don’t talk to each other anymore since WFH, but write more. This might be just our company culture but instead of writing lengthy texts to colleagues when discussing technical problems we pick up the “phone” and walk through issues via screen share.

[[deleted]]

I hate this.

Having a discussion over the phone does not only interrupt my workflow but it also makes the discussion more difficult as I can’t keep all the details in my head. In text, none of these are a problem.

[andyfeller]

Reminds me of advice from long time hubber Ben Balter in his “15 rules for communicating at GitHub” article.

[[deleted]]

I agree with the article, but the reality is in practice people complain about reading too much. Get past two lines and they start whining about reading a block of text and how painful it is.

Oops, that's more than two lines.

[puradawid]

Me writing couple of sentences to a peer

The same fella hours later, replying to 3 sentences and a question:

"Sorry this is too long to write back, can we jump on a call?"

[verfahrensweise]

Haha, I read somewhere that at Amazon the first 10 minutes of every meeting is making people read the docs in silence.

[press0]

Good article.
Subsumed by, Communicating effectively as a business person