Some of this is not new, but it looks like a dying practice. It doesn't need to be. This medium is more efficient than chat for some cases.

I like this piece. In most case it's the thinking which is important not the writing. So even if the language is subpar it's better if you write yourself... except if it's not worth the effort in the first place.

A bit cynical at times, but shows tricks to improve the writing and style of blog posts. If I ever find the time to write something sizeable again I guess I'll try some of them.

Good explanation of why the passive voice should be avoided. Also it gives a few cases where you want to favor the passive voice.

Interesting proposal of structure for technical documentation.

Need to write a tutorial? Here is a good set of rules to follow. Don't be fooled, it sounds simple but it is hard work.

Very extensive guide on writing better commit messages. This is important, it's a very central communication mechanism with other developers.

Good advices to improve writing. I should apply such rules to myself more often.

Pick your words wisely. If it does happen every time use "will".

Interesting advices about creativity. The metaphors used help a bit as well.

All the good reasons to have a blog. This is why I keep maintaining mine.

Indeed, this is the most important skill we need next to coding. Especially in a remote work culture.

A reminder for me, I write quite a bit, but I feel that I don't write nearly enough. It's very important for plenty of cases though.

If you like remote work, then you need to make sure your written communication is good. There's a handful of proper guidelines in this paper. Good reminders.

OK, this is a neat and simple trick. I think I'll start experimenting with it.