Naomi Florence

Pulling from comments + makers is powerful but messy. How do you decide what signal to prioritize?

Focusing on backlog execution instead of suggestions feels like a much more practical direction. That's where things usually get stuck.

Is clarity being sacrificed for speed and scannability?

I am not fully convinced novelty is always bad. Sometimes it's just ahead of the workflow people have not formed yet.

Hot take: weekend streak drops might not be a problem, could just mean people are living more freely?

Interesting shift, but without clear attribution, convincing clients long-term might get tricky.

This is a good reminder that "confusing" feedback is often more valuable than praise. What part of the flow got misunderstood first?

The $50k floor is probably what makes this feel real. That changes it from a nice idea into something founders might actually prioritize.

Curious how you balanced this without making it feel too much. That seems like a very fine line to get right.

This was a useful read. A lot of people talk about building fast with AI, but not enough people talk about where speed starts creating hidden cost.

The API cost spike is such an underrated failure mode. A lot of AI generated code is "correct" in a way that becomes financially stupid in production.

Sometimes I don't even need a full demo, just one s.s or use case that makes the value obvious is enough. Do you think too much polish can actually slow decisions making?

"Don't niche down too much" was terrible advice for me because broad messaging usually just made the product easier to ignore. Did things improve once you got more specific?

I think the biggest issue is not posting once in a while, it's when visibility starts becoming an unspoken part of job performance. Have you seen that happens already?