Amanda Phillips

One of the toughest parts of scaling a community or a product is managing the feedback loop. You want the raw, unfiltered truth from your early users because that's the only way to fix broken features, but sometimes the feedback is just... harsh.

As founders and builders, how do you filter out the unhelpful noise from the constructive criticism? And more importantly, how do you pass that feedback along to your engineering or design teams without killing the momentum?

Honest question for this forum.

I save AI tool threads constantly. New model drops, someone's slick Cursor workflow, "10 tools that'll change everything." I open maybe one in twenty. And I still feel behind every single week.

Lately I think the problem isn't information, there's an ocean of it. The problem is that almost all of it tells you about AI instead of showing you. A thread describes a workflow. A launch video is scripted so everything works on the first try. None of it shows the real thing: the prompt someone throws away, the tool they reach for and why, the moment it breaks and how they dig out.

And that's the part that actually teaches you. Nobody got good at cooking from recipes or at chess from the rulebook. You get good watching people better than you do the real work.

Vibe coding makes it much easier for non-technical founders to build a first version, test an idea, and get real users without hiring a full engineering team.

But what happens when the product starts working?

You have users. Maybe even paying customers. People depend on it now. But the app starts slowing down, bugs become harder to fix, and adding new features feels risky because the codebase was built mainly to validate the idea.

At that point, the question is no longer: Can this be built?