How to write blog posts that developers read

Ironically I opened the post, read the headlines, deemed it uninteresting and went along with other HN headlines.

edit: I think I read HN comments more than HN articles. Interesting

Author here.

Your comment suggests that you at least read the last section. : )

But still, that's headings and structure working as intended: You skimmed it, got a good sense of what it's about, and decided it wasn't for you.

I'm assuming that if I had presented the same information in a different way, it still probably wouldn't have appealed to you if you could tell from the headings that you weren't interested.

> edit: I think I read HN comments more than HN articles. Interesting

Nothing wrong with that, in my opinion.

I always check comments first before clicking the link, unless it's something I'm knowledgeable about and/or interested in and already know I want to read. It saves a lot of time.

Sample size 1. To increase to 2:

I opened it, read enough to establish this author knows what they are talking about and bookmarked it to read properly before my next blog post.

Had they told me the blogging equivalent of their intergenerational nanna's spaghetti recipe first I may not have done that.