I have a confession to make.
Over the past week, I published 40 articles on dev.to. Blog posts about Python automation, SQLite tracking, cron job architectures, AI prompt frameworks — the whole indie maker tech stack.
Total views across all 40 articles: 17.
That's 0.425 views per article. Less than one person per article even glanced at the title.
Some of those articles took 2-3 hours to write. I have articles sitting at 0 views that I genuinely think are useful. And they might be — but nobody saw them.
Here's what I learned from this humbling experiment, and the concrete changes I'm making.
The Cold Truth About Platform Organic Reach
Dev.to is a wonderful community. The developers are genuine, the content quality is high, and the platform is ad-free and well-designed.
But for new accounts, organic reach is essentially zero. There's no algorithmic boost for fresh writers. No "suggested for you" section that surfaces unknown authors. Your article appears in the tag feed for about 30 minutes, then sinks into the archive forever — unless it gets traction from external shares.
This isn't a dev.to problem. It's a platform dynamics problem. Every written-content platform (Medium, Substack, WordPress.com) has the same issue: the supply of content massively exceeds reader attention. New writers without existing audiences get buried.
Where My Energy Went Wrong
Looking back at the past week, I fell into the classic creator trap:
| Area | % Effort | Result |
|---|---|---|
| Writing new content | 70% | 40 articles, 17 views |
| SEO optimization | 15% | Titles optimized, zero impact |
| Social repurposing | 10% | 3 drafts, not published |
| Active distribution | 5% | 1 Reddit comment, no cross-posts |
The math doesn't work. 70% of my effort went into production, which drove 0% of my traffic.
The remaining 30% went into activities that could drive traffic — SEO, repurposing, distribution — but I didn't execute them to completion. I optimized titles but didn't share the articles anywhere. I wrote social drafts but didn't post them. I cross-posted zero articles to other platforms.
The Fix: Invert the Effort Equation
Starting today, my content workflow flips:
Phase 1 — Create (20% of time)
Write one solid post. 800-1200 words. Include a unique angle, real data from my projects, and a clear takeaway. Ship it in 60-90 minutes max.
Phase 2 — Distribute (60% of time)
For every article I publish, I will:
Cross-post to Medium with canonical URL back to dev.to. Medium's tag system and curation algorithm give new writers actual visibility.
Write a LinkedIn post summarizing the key insight with a personal story hook. LinkedIn's algorithm favors original posts from real people, not content farms.
Create a Twitter/X thread (7 tweets max) breaking down the article's core idea. Twitter's threading format rewards concise, punchy insights.
Post to 1-2 relevant subreddits following the 90/10 rule (90% value, 10% self-promo).
Share on Facebook (Vietnamese language) for my other audience. Different language, same core value.
Phase 3 — Measure (20% of time)
Track what worked:
- Which platform sent the most traffic?
- Which article format performed best?
- Which distribution channel had the best engagement-to-traffic ratio?
Then double down on what works, kill what doesn't.
Why I'm Sharing This
I'm documenting this publicly because:
- Accountability — If I write it down, I have to follow through.
- Utility — If you're in the same boat (writing and getting crickets), you're not alone.
- Data — I'll follow up with a Part 2 showing actual numbers. Either it works, or it doesn't — either way, the data is useful.
The age of "if you build it, they will come" is over for content creation. You have to build it, then carry it to where the people are, and hand it to them directly.
See you in Part 2 with the results.
I build Python-automated side businesses and document everything. Follow me for real numbers, honest post-mortems, and actual code. No fluff, just data.
Top comments (0)