Zero to 39 Repos — What I Learned

In less than a year I went from no public GitHub presence to 39 repositories across Python, TypeScript, JavaScript, and C#. What I'd tell myself at repo #1.

Ship ugly things

The first few repos are embarrassing in retrospect. That's correct. The goal of repo #1 through #10 is to build the habit of finishing and shipping, not to build impressive software. Impressive comes later. Finishing first.

Breadth before depth

I deliberately spread across languages and domains early. Python agents, TypeScript frameworks, .NET APIs, HTML experiments. This felt scattered but it was actually the right call. Patterns transfer. A good abstraction in Python teaches you what to look for in C#. Cross-pollination is real.

Documentation is a first-class deliverable

The repos that get attention — even small amounts — are the ones with clear READMEs. Not long. Clear. What it is, why it exists, how to run it. Three minutes of writing per repo dramatically changes how useful it is to anyone including future-you.

What changes around repo #20

Something shifts around the midpoint. You stop asking "what should I build" and start noticing gaps — things you wish existed, tools you keep rebuilding from scratch, problems you've solved twice that deserve a proper solution. The project ideas get better as you accumulate more surface area.

The compounding effect

Each repo is practice. Each README is practice. Each architecture decision compounds into intuition. By repo #39 the gap between idea and implementation is smaller than it's ever been.