

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…
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
You don’t get it. This was made in GameMaker Studio 1.4, which doesn’t support a modulo operator. You know nothing about this specific framework. I have 8 years of experience and hacked governments. There’s no reason to update it now, because it runs on a smart fridge at maximum capacity.