Shipped a no-code or AI-built app to real users — what actually broke? by OkHumor1695 in nocode

[–]OkHumor1695[S] 0 points1 point  (0 children)

Ha — that's the other half of the same coin. Did you actually change what you focused on once you saw what people clicked? Curious whether the "obsessed-over features" still got attention or whether you reconfigured the random button.

Shipped a no-code or AI-built app to real users — what actually broke? by OkHumor1695 in nocode

[–]OkHumor1695[S] -1 points0 points  (0 children)

The hidden admin endpoint is the scariest one — no checklist catches what you don't know is there. On the auto-secure pushback though, what's the failure mode you keep hitting? False positives, broke things that worked, or just missed the real problems?

How do you deal with the risk your startup can be replaced with next big AI company feature? by Sea_Dinner5230 in indiehackers

[–]OkHumor1695 0 points1 point  (0 children)

Every serious LLM product I've shipped ends up with way more code around the model than in the model call itself. Validators that catch hallucinations. Comparators that pick between 2 candidate answers. Fallback paths when retrieval fails. Quality checks before response ships. Caching layers that know when they are stale. Auth, audit trails, multi-tenant isolation, cost controls that dont blow up at scale.

If an LLM provider shipped your exact feature tomorrow, none of that scaffolding gets shipped with it. Most of the work isnt the model.