Jitendra Kumar

We spent months debating whether to ask for credit card info upfront. When we finally removed the card requirement, our trial sign-ups shot up by 300%, but activated users barely changed.

It turns out lower friction just filled our pipeline with ghost users who never actually set up their account. Adding a bit of friction back actually improved lead quality and reduced support load.

Have you noticed better long term retention with high friction or low-friction onboarding?

Vibe coding lets you spin up functional tools fast but tracking down sudden bugs can be a total nightmare.

When an agent updates a file and breaks a working feature finding the root cause usually wastes more time than writing the code from scratch.

I'm trying to figure out a lightweight testing workflow like basic test cases or background eval scripts that keeps things reliable without slowing down the build speed.

If you build apps using AI coding assistants how do you handle testing and error tracking when a feature stops working?

API costs can get surprisingly high as an app grows so self-hosting open-source models starts to look attractive. But cheaper inference doesn't always mean cheaper overall. You still have to think about GPU costs server maintenance traffic spikes and whether the model gives users the same quality of results. For a small app paying per request feels easier. But once usage grows I wonder if managing your own infrastructure becomes the better option or just creates another problem to maintain. For those who have tried both what made you switch and did self-hosting actually reduce your total costs?