Documentation? Maintainable? Test cases? You're too attached to old paradigms in a new vibe based world.
Why do you need any of those? If you need any new features, you just re-engineer your prompt and ask the AI to rebuild it from scratch...
Can someone explain how you accidentally rack up such a bill?
For example: You can deploy your Python script as a Lambda. Imagine somewhere in the Python script you'd call your own lambda - twice. You basically turned your lambda into a Fork Bomb that will spawn infinite lambdas
A lot of the times this comes down to a user error.
For example, very similar to your case, I knew someone that enabled Cloudtrail, and configured some things to have Cloudtrail logs dumped on S3. Guess what? Dumping things on S3 also creates a Cloudtrail that gets logged to S3 that Cloudtrail logs. Etc
Doing things like that and creating a loop can get you massive bills
From a sales perspective it makes sense... What percentage of the female tinder users would have Tinder Premium compared to men? I'd think the numbers are very lopsided.
And women don't need the other Premium features of "Getting more swipes per day" or something, because they'll get plenty of matches every day anyways. If they want to sell more Premium to women, adding features that might interest women behind a paywall is a smart move
Since you're getting downvoted, maybe you want to explain why using Github free is "pointing a loaded gun at your foot"?
I'm using github for a bunch of my public repos as a free backup service... Why would I want to use a self hosted or way more obscure git forge? Seems riskier than just dumping it on github