The instinct when you start something new is to build it in private until it's presentable — get the rough edges sanded off, write a decent README, maybe wait until there's something that actually works before anyone else sees it. It's a reasonable instinct. It's also not how anything in Link with iQ gets built.

Every repository here starts public on its first commit. That means the messy, half-working, "does this even run" version of Community Toolkit is sitting in the same place as the version that eventually ships. Anyone can watch a project go from an empty folder to something usable, mistakes included.

What this costs us

It's a little uncomfortable, honestly. There's a specific kind of vulnerability in pushing code you know isn't good yet, knowing it's attributed to you, permanently, in a public history. It would be easier to batch up the good parts and present a clean story.

There's also a practical cost: writing commit messages and code comments as if someone unfamiliar with the project might read them today, not eventually, takes more care than writing purely for yourself.

What it buys us

A few things that seem worth the discomfort:

  • No orphaned work. If a project stalls — and some will — the code doesn't disappear with it. Anyone can pick up where we left off.
  • Real accountability. "It's open source" is a much easier claim to make than to actually do. Starting open makes it true by default instead of by decision later.
  • Feedback earlier than feels comfortable. Someone pointed out a genuinely bad approach in Snippet Library's first week, before we'd built three more things on top of it. That only happens if the code is visible early.
The alternative to "open from day one" isn't really "open once it's polished." In practice, it's often just "open never," because the bar for polished keeps moving.

What this doesn't mean

Open by default doesn't mean every idea gets a repository. Plenty of things get discussed, sketched, and dropped before a single line of code exists — that part stays private, because half-formed ideas in someone's head aren't useful to anyone else yet. The line we draw is: once we start building, we build in public.

If you want to see what that actually looks like, the commit history on any of our active projects is right there. Read it, judge it, or borrow from it — that's the point.