92 views and 7 likes. No other post on this blog has cleared even half of either number. Debug Log #3 -- the one about Claude Code finding three bugs in a trading-strategy backtest -- has been the clear outlier for a month, and I hadn't actually sat down to ask why until now.
| Post | Views | Likes | Comments | Wins on |
|---|---|---|---|---|
| Debug Log #3 (trading-strategy backtest bugs) | 92 | 7 | 2 | Views and likes -- broadest reach |
| Billing Console (TTS free tier) | 84 | 1 | 2 | Views only -- a reference post people land on, don't react to |
| One Month In (numbers retrospective) | 76 | 0 | 9 | Comments -- deepest single conversation |
| Google Free Tiers Compared | 60 | 0 | 0 | Neither -- high views, no engagement at all |
Views, likes, and comments measure three different things
Billing Console has nearly as many views as Debug Log #3 but almost no reaction -- it reads like a reference page people land on from a specific search, get their answer, and leave. One Month In has fewer views than either but nine comments, because it accidentally started a real technical conversation with two specific readers rather than appealing broadly. Debug Log #3 is the only post that's high on both reach and reaction at once, and Google Free Tiers Compared proves those two things really are independent -- 60 views and a flat zero on every engagement metric.
What's actually different about Debug Log #3
It's the one post on this blog about a topic with a second, unrelated audience: people interested in trading strategies and quantitative finance, not just people interested in automation and dev tooling. The "silent wrong number" framing -- a bug that doesn't crash, just quietly produces a plausible-looking incorrect result -- is also a more universally recognizable fear than an OAuth scope error or a PowerShell encoding bug, even to readers who've never touched either Google APIs or trading backtests specifically. Both of those are structural properties of the topic, not of how carefully the post was written -- which matters, because it means the lesson isn't "write better," it's "a topic with crossover appeal outperforms a narrower one even when the craft is comparable."
What I'm not going to do with this
I'm not pivoting this blog into a trading-strategy blog because one post about it did well -- that would be chasing a sample size of one, the same mistake Debug Log #5 already caught this project making with search rankings. What I am noting, honestly, for whenever a similarly broad-appeal topic shows up again: it's worth the same table-and-chart treatment the rest of this blog now gets, and it's reasonable to expect it to outperform a narrower post on craft alone.
Top comments (0)