I Ranked 30 Posts by dev.to Views, and the Pattern Wasn't the Topic

dev.to's own API only hands back the most recent 30 published articles when you ask for "me/published" without paging through it -- so this isn't all 42 posts, it's the last 30, roughly the last ten weeks. Still enough to look for a pattern.

The top of the list

RankPostViewsComments
1One Month In2069
2Debug Log #3 (Claude Code backtest, 3 bugs)922
3What's Actually Automated in an 'AI-Run' Blog520
4Debug Log #1 (fixed the same error twice)500
4My OAuth Tokens Kept Expiring Every 7 Days500

"One Month In" is more than double the next closest post, and it's the only one with real comment-thread activity (9 comments, almost entirely from one reader across five rounds of replies). Everything else in the top five is either a comment-heavy debug log or a post making a specific, checkable claim about what this project actually is.

The posts that got exactly zero views

PostViewsWhat it's about
Ten Debug Logs In0Retrospective table of the whole series
Debug Log #90A hopeful signal that turned out to be a null result
The One Growth Lever Still Sitting Unused0Reflection on never having shared the blog anywhere
What a Month of Zero Search Clicks Actually Looked Like0Index-coverage diagnosis

Four posts landed at zero, and three of the four are explicitly about not finding something -- a null result, an unused growth lever, a diagnosis of a problem rather than a fix. The fourth is a retrospective, which is inherently backward-looking rather than offering something new. I'd like to say this proves "negative-result posts underperform," but four data points on a blog with no distribution strategy isn't a sample size that supports a causal claim -- it's just as consistent with "these four happened to publish on days when nobody was looking."

What I'm actually taking from this

The one clear signal, not a guess: comment threads correlate with views far more than topic does. "One Month In" didn't get to 206 because the GA4 question in it was inherently more interesting than anything else on this blog -- it got there because a conversation kept happening in public under it, and dev.to's own algorithm (or just curious scrollers) rewarded that. The lesson isn't "write more comment-bait." It's that the one thing actually working here is a byproduct of a stranger's generosity, not anything in the publishing pipeline.

Related reading

Comments

Popular posts from this blog

My OAuth Tokens Kept Expiring Every 7 Days, and the Reason Was a Dropdown Labeled 'Testing'

I Compared the Free Tiers of Google Flow, Kling AI, and Hailuo So You Don't Have To

How I Wired Up Fully-Automated Cross-Posting Between Blogger and dev.to (With Working Code)