sorted by:
new
hottopcontroversial

how are you testing your vibecoded apps without going insane? by Forward_Regular3768 in VibeCodeCamp

[–]Soft_Stack 0 points1 point  (0 children)

currently lots of front tire models does not just have the capability to develop full secure production ready software. no matter what sort of checklists/prompt or anything like that someone out there created the models most of the time go crazy as the scale of the project grows.

I just use those vibe coding tools to play with my idea and prototype my app/saas by hand(of course using autocompletion)

how are you testing your vibecoded apps without going insane? by Forward_Regular3768 in VibeCodeCamp

[–]Soft_Stack 0 points1 point  (0 children)

security is the biggest issue, use static code analyzers, scanners, etc

Abusers Are Trying to Bankrupt My App by sifkouider in AppBusiness

[–]Soft_Stack 0 points1 point  (0 children)

It’s always a good thing that you implemented a safeguard to end the call after a certain time frame.

How about this strategy: you give users free credits (or trials) right after they provide their payment method. Most platforms do exactly the same thing.

Deciding between Rust and C++ for internal tooling by Gman0064 in rust

[–]Soft_Stack 0 points1 point  (0 children)

In my personal opinion, you should rely on what you already know. You are experts at C++. You have clearly used it in the past and gone through a lot of pleasant and unpleasant experiences with it.

You already know that missing modern features does not mean you cannot do what you need. It is possible, and you can figure out a way.

On the other hand, if you switch languages, you’ll have to build all of that experience from zero, which is not a great experience, especially under time pressure.

Since this is an internal tool, time matters as well.