Gulshan Singh

Early on, we treated every user request like an urgent priority, only to realize later that custom features didn't even stop those users from churning. Building what people ask for instead of solving their actual root problem destroyed our focus and wasted months of dev time. If you run a small product team, what framework do you use to filter out isolated demands and keep your core vision intact?

In the RunEvr team, we're all problem solvers.

I honestly don't remember an exciting problem we've left without a solution =D

Been deep in the problem of spotting AI-generated or copied answers, and a few things genuinely surprised me. Sharing in case it s useful, and because I d like to hear how others are handling it.

First, asking nicely does nothing. Telling a model, or a person, not to use outside help just gets ignored, the instruction has no teeth.

Second, a single answer tells you almost nothing. One polished response could be real or pasted, with no reliable way to know in isolation. The signal only shows up across a whole session, consistency, timing, how close the answer sits to what a tool would generate.

Third, follow-ups are the real test. Pasting one good answer is easy, but holding it up through two or three why s is where the rehearsed stuff falls apart.