TechBlast - Tech News for Builders and Operators

3 days ago I published my first dev.to post: "I built a self-growing Japanese brand database in 1 hour with Lovable (0 customers, 0 followers)."

The stats today:

Views: <25
Reactions: 0
Comments: 0
Followers: 0

Here's the honest breakdown of what didn't work, and 3 things I'm changing.

1. Passive doesn't work

I published and waited. No X share, no Reddit, no Indie Hackers (got blocked there anyway as a new account).

The lesson: dev.to alone doesn't distribute itself. It rewards momentum signals — comments, reactions, external traffic. New accounts with no signal stay invisible.

What I'm changing: Today I shared the post on X with a question to indie builders. Tomorrow I'll add genuine comments to 5 #showdev posts I actually find interesting.

2. The title was about me, not them

My old title: "I built a self-growing Japanese brand database in 1 hour with Lovable (0 customers, 0 followers)."

Self-centric. About my journey, my tool, my emptiness.

What works on dev.to: titles framed as the reader's problem or technique.

What I'd write today: "How I auto-enrich a brand database with AI on cache miss (Lovable + Claude API)"

The reader benefit is clearer. The technique is upfront. Use case comes second.

3. I forgot the audience

dev.to is developers. My customers (Amazon sellers) are not.

I wrote about my product like a product person, not a developer. Devs scrolling the feed don't care about Japan sourcing — they care about the pattern I used to build it.

What I'm changing: For my next post, I'll lead with the technical pattern (AI-powered DB enrichment on cache miss) and let the use case come second.