I've been writing / editing technical blogs for the past decade, and I found that the key thing is to be engaging.
Most technical blog posts are boring. They look like documentation.
My best technical blog posts were the ones where I added personal stories about how I used the library/framework I was referring to.
The best advice from OP is to hire an editor. Especially for non-native English speakers (like me). A good editor can transform "good" technical content into exceptional content.
Most technical blog posts are boring. They look like documentation.
My best technical blog posts were the ones where I added personal stories about how I used the library/framework I was referring to.
The best advice from OP is to hire an editor. Especially for non-native English speakers (like me). A good editor can transform "good" technical content into exceptional content.
Michael Lynch, who regularly front-page HN has a great article about this: https://mtlynch.io/editor/