The Eternal Collector

"Why build it when you can fork it?"

vibe Has an "awesome-lists" repo with better docs than anything they've built.

Your GitHub is 80% forks. You've starred 2,000 repos you'll never open again. Great taste, questionable output. Curation is a skill, but at some point you have to actually make something.

Typical stack

starred repos forked tools Notion databases RSS feeds

Known examples

sindresorhus/awesome The original — but Sindre also ships. That's the difference.

Signature traits

→ Starred repos outnumber commits 100:1
→ Fork count in the dozens, contributions to those forks: zero
→ Has a "resources" or "awesome-lists" repo with a great README
→ Bookmarks Hacker News submissions compulsively

Strengths

✓ Genuinely excellent taste in tools and libraries
✓ Can find a library for anything in under 3 minutes
✓ Great at evaluating tools before committing to them

Watch out for

⚑ Collecting ≠ building — your profile doesn't show what you can do
⚑ FOMO-driven — always waiting for the "better" tool before starting
⚑ Star lists don't survive technical interviews

How to level up

Stop starring, start using. Pick three repos from your starred list and actually implement something with them. Then close the browser tab. The best way to evaluate a tool is to build something real with it.

Is this you? Find out for real.

Roast my stack

← All archetypes