SebastianVerified account

Thinking about it more, there's probably not a lot I can do to prevent it. And doing an "impromptu" release could have the opposite effect. If I didn't want any expectations then I shouldn't have spoken publicly about it at all. That's the main reason I didn't prior.

I don't want early access. I'm afraid of building an ivory tower of privileged people. For Yarn we invited people at the beginning. It allowed them to influence the development process but we overrotated on their feedback.

It's possible to select people who are the most relevant, and I felt like we did. The feedback was valuable, but they weren't necessarily the ones who would actually be invested post-release.

So I spent time satisfying their constraints which would turn out to not be relevant. Again, this can be mitigated if you have a more cohesive community where everyone is mostly on the same page.

Another point is around inclusivity. I don't want anyone to feel left out. No matter how wide you cast the net, there's always going to be someone valuable you've left out. Performing value judgements on people is gross and not really something I want to have to do.

Especially since position in the community, which most use as a measure of relevancy, doesn't necessarily yield the most useful feedback.

I've never received private feedback that wouldn't have been more valuable to have publicly. Once your community reaches a certain size that can be extremely noisy though.

Also depends on the release position of the project. Rome would probably be released as an alpha or beta. Opportunity to change anything, which is typically the purpose of early access.

I feel as though I have the necessary experience and context to build a functional MVP. Any public or private feedback during that time would be unlikely to be unproductive.