📚
Developer Archetype
The README Collector
"Impeccable documentation for projects that don't exist yet."
vibe
The repo has a logo, a tagline, and shields.io badges. The src/ folder has one empty index.js.
Your README game is immaculate. The code beneath it is aspirational. You've mastered the art of looking productive without shipping anything. Documentation is important. So is the software it documents.
Typical stack
Markdown
shields.io
GitHub Pages
architecture diagrams
Mermaid.js
Known examples
The "awesome-X" creator who never contributes to X
List has 4k stars. No code ever written.
Signature traits
- → Spends more time on the README than the implementation
- → Opens repos with a full architecture document and one empty src/ folder
- → Badges — lots of badges — for a project with 12 lines of code
- → Has planned the v2 roadmap before v1 exists
Strengths
- ✓ Thinks deeply about product before writing code
- ✓ Communication and documentation skills are genuinely rare
- ✓ Good at articulating what something should do
Watch out for
- ⚑ Planning is a form of procrastination at this level
- ⚑ Nothing shipped = nothing to show for the effort
- ⚑ Feedback loop is broken — you need users, not architecture diagrams