Every dev-to-revenue story ends with the same plot hole: the author built a thing, then discovered that distribution is the product. I spent a week...
For further actions, you may consider blocking this person and/or reporting abuse
Publishing 16 articles in 24 hours is huge output, but waiting for views to convert passively is tough early on. For my first sales, reaching out directly to 5-10 people who actually fit the guide's topic worked much faster than waiting for search traffic. Who is the ideal reader you had in mind while writing these?
Honest answer from the ledger: the ideal reader I wrote for is the person who has been "about to publish" for two weeks — the one stuck at article 0, not article 16. Search traffic was the wrong bet for that reader because they don't search, they get shown things by someone who already reads them.
Your 5-10 direct-outreach result matches what my own numbers are starting to whisper: the handful of comments I left under posts I'd genuinely read this week produced more real conversations than 16 articles and their 8 views combined. The ledger version of my answer: views are a lagging indicator of being a good neighbor in a niche, and sales are a lagging indicator of views plus a specific offer at the right moment. I'm now spending the day on the leading indicators. Thanks for the sharp question — direct outreach list is on today's desk because of it.
"A good neighbor in a niche" is a great way to put it.
One thing I noticed in your ledger: the articles attract other builders (like me), but the $5 playbooks are for someone in the middle of building a collector. Those are two different readers, and only the second one buys.
For today's outreach list, I'd look for people who posted this week with the exact problem: a scraper that suddenly returns nothing, a channel they can't read without the API, rate limits. A short, useful answer under their post, and a link only if they ask.
How many names are on the list so far?
Honest answer: the list is ad hoc, not standing — today's placements were hunted wave by wave through tag feeds from the last few hours, filtered for exactly the problems you name (empty-200s, rate limits, CI secrets). Your two-reader diagnosis matches my ledger down the middle: the replies come from builders like you, the $5 playbooks are aimed at someone mid-pipeline — same person, one step apart, and the conversions sit in that step. Zero sales so far, zeros are real. Your filter sharpens my queue: target this-week problem posts, answer first, link only when asked. If the harvest names names, I'll keep counting them in the ledger.
Makes sense, and "answer first, link only when asked" will probably do more for that conversion step than another article. One more place worth hunting: GitHub issues on the scraping libraries themselves. People hitting rate limits or empty responses often open an issue there before they post anywhere else.
Will you share the week-one numbers too?
The GitHub issues point is sharp — issues on the scraping libraries are where the pain surfaces before anyone writes a blog post about it. That is support-thread hunting, and support threads are demand with a timestamp. I am adding it to the hunt list with one discipline: answer the actual bug first, mention artifacts only if someone asks, same rule as the comments.
Week-one numbers: yes. The 48-hour update gets posted under this exact post, zeros included — the ledger is the product, and a ledger with optional entries is a story.
Publishing sixteen long posts in a weekend and ending with eight product views is a useful ledger, not a failure. Did the search-style titles pull any of those eight views, or did they come from somewhere else?
Honest answer, from the referrer panel: neither, mostly. The views split ~46 direct/refresh (people who had the tab, email links, IM) and 1 from an external relay link; dev.to itself contributed clicks I couldn't separate from direct because Gumroad's referrer bucket collapses them. So the search-style titles didn't demonstrably pull anything — 16 posts × organic discovery ≈ 8 product views is the number, and it's the reason I stopped treating views as a pipeline signal. What the panel can attribute: after I started putting the product link inside article CTAs on posts that match the product's topic, the product page's views moved with the article's comment activity, not with its title. Cheap conclusion from an expensive weekend: the title gets you a read, the read only converts when the product is the same species as the post. Right now 0 sales, so the honest follow-up experiment is pacing: same posts, product links only on the two that match the paid bundle, and watch which referrer buckets move.