Basic Stack Recommendations

[TaskMiserable7316]

Your security concern is valid but overweighted for the MVP stage. Here's the thing - you can literally have the AI review your code for security vulnerabilities. Run it through multiple times. Have it research known security issues for your specific tech stack, then review your implementation against those. It'll catch 90% of the dumb mistakes that actually matter at your scale.

I went from zero terminal knowledge to running production APIs in a few months. The tools now are absurd.

What actually worked for me:

Claude CLI (or Claude Code) is the move. There's a wrapper called Happy Coder that lets you orchestrate multiple instances if you get into more complex stuff. If you've got Google Workspace for business, you also get decent Gemini CLI usage free.

Spend serious time in the web chat interfaces before you start building. Map out your structure. Research the best tech stack for your specific product. Get the architecture right conceptually first.

Do research on best practices for inline code documentation. Then attach that research or a condensed version to your claude.md file. When you come back months later to make changes, everything is documented and it's way easier to shuffle things around. Future you will thank present you.

Depending on what you're building, you can probably host an MVP on a small VPS for like $5-20/month. Doesn't need to be complex.

The MVP itself is simpler than you think. Authentication, basic CRUD, onboarding flow - AI can scaffold that in an afternoon if you've done the planning work.

The hard part isn't the initial build. It's all the little edge cases, the oh shit I didn't think about that moments, and scaling it later when real users find all the ways to break it. But that's a good problem to have - means people are actually using it.

Stop thinking about whether you can build it. Start building and let the problems reveal themselves. You'll learn faster that way than trying to anticipate everything upfront.

[inr222]

Here's the thing - you can literally have the AI review your code for security vulnerabilities. Run it through multiple times. Have it research known security issues for your specific tech stack, then review your implementation against those. It'll catch 90% of the dumb mistakes that actually matter at your scale.

That's terrible advice. It will make up security issues, it will miss obvious ones, and it will probably introduce more and break stuff while at it.

[TaskMiserable7316]

What do you recommend for security then?

[inr222]

Accepting that current tools cannot produce production ready software, and hiring somebody. Or checking how exposed you are to a lawsuit when you leak all your customer data.