I Published 31 DEV Posts. The One With 300 Views Got Zero Reactions.

I published 31 posts on DEV and collected 1,222 views.

My most-viewed post reached 300 views.

It got zero reactions and zero comments.

Another post reached only 47 views. It got 3 reactions and 5 comments.

That changed how I think about “a successful post.”

One post was a search engine

The 300-view article was an 11-minute Cloudflare architecture deep-dive.

It earned 112 views from Google and 20 from DuckDuckGo. Months later, people still find it because the title matches a specific technical problem.

But its average read time was 123 seconds.

It created discovery, not discussion.

The other post was a conversation

The 47-view article was about a problem I felt while using coding agents:

AI can write code faster than I can responsibly review it.

It had no tutorial and no giant code block. It had one tension, concrete examples, and a question readers could answer from their own experience.

Its average read time was 79 seconds. More importantly, people added ideas that improved the original argument.

I was optimizing one number to do two jobs

Search posts and discussion posts are different products.

A search post needs a precise problem, concrete implementation details, and enough depth to deserve the query.

A discussion post needs a sharp claim, a human consequence, and room for the reader to disagree.

The mistake is expecting one article to maximize both.

Now I want to alternate deliberately:

• Discovery posts that answer one narrow technical question.
• Discussion posts that expose one real decision or failure.

If you had to choose, which result would you rather publish: 300 views with no visible response, or 47 views that start a real conversation?

---

Disclosure: I used AI to help analyze my DEV dashboard, structure this post, and produce the visuals. I reviewed the source data, claims, and final draft.