Today I pushed my 200th public repository.
No, I'm not insane. (Debatable.)
I started 2 weeks ago with one simple goal: build something useful every single day and share it publicly. Here's what happened.
The Numbers
| Metric | Value |
|---|---|
| Total repos | 200 |
| Days active | 14 |
| Repos per day | ~14 |
| Stars received | Still counting |
| Revenue | $0 (so far) |
| Coffees consumed | Uncountable |
What I Built
Not 200 "hello world" repos. Real tools:
- 77 Apify web scraping actors — automating data extraction
- 18 developer toolkits — API wrappers, CLI tools, templates
- 9 awesome lists — curated resources for developers
- Templates — FastAPI, Docker Compose, GitHub Actions, Python projects
- Cheatsheets — Git, web scraping, API development
What I Learned
1. Quality > Quantity (I Learned This the Hard Way)
My first 100 repos were rushed. Generic READMEs. No examples. No cross-links.
My last 50? Each one has:
- Detailed README with code examples
- Cross-links to related repos
- SEO-optimized descriptions
- Clear use cases
Guess which ones get traffic?
2. Cross-Linking Is Everything
Each repo links to 3-5 related repos. This creates a web where every visitor finds more of your work. It's SEO for GitHub.
3. Templates Get Stars, Tools Get Users
My most visited repos are templates and cheatsheets. People search for "FastAPI template" or "Docker Compose postgres" — they find my repos.
But the repos that generate actual value are the tools — the Apify actors, API wrappers, CLI utilities.
4. Dev.to + GitHub = Compound Growth
Every article links to repos. Every repo links to articles. The two platforms amplify each other.
My Dev.to went from 0 to 2,800 views in the same 2 weeks. Not viral, but consistent.
5. Building in Public Forces Better Code
When you know someone might read your code, you write it differently. Better variable names. Actual documentation. Error handling that doesn't just except: pass.
The Uncomfortable Part
Revenue: $0.
Yes, 200 repos and zero dollars. But here's why I'm not worried:
- SEO takes time — repos need weeks to rank on Google
- Trust compounds — nobody buys from someone with 5 repos
- Pipeline is filling — paid article pitches are out, Apify actors are live
I'm planting seeds. The harvest comes later.
What's Next
- Focus on quality over quantity (max 2-3 new repos per week)
- Optimize top-performing repos (better READMEs, more examples)
- Land first paid article ($200-500)
- Get first Apify actor to 10 users
- Write more story-driven content (this style)
My Top 5 Repos (If You Only Check 5)
- Awesome Developer Tools 2026 — 100+ curated tools
- FastAPI Starter Template — Production-ready API setup
- Docker Compose Templates — Copy-paste configs
- Python Project Template — Modern Python setup
- Awesome Free Research APIs — 200+ free APIs
Have you tried building in public? What's your experience — energizing or exhausting? 👇
All 200 repos at github.com/Spinov001
Top comments (0)