Rule #1: Always put deletions behind a flag which is disabled for the first couple of test runs.
turtleyacht · 4h ago
It was truncating filenames, so /pics/1003-46.png overwrote /pics/1003-45.png because both were renamed /pics/1003-.png, or something like that.
qwertox · 3h ago
Truncating file names for the target. Then it proceeded to delete the source file.
"Successfully deleted local file: ..."
I mean, look at the printout. It shows that it created the remote file with the truncated filename, then deletes the local file with the correct filename.
turtleyacht · 3h ago
Oh, I see. Having a flag to skip deletion during test runs is a good rule then.
victorbjorklund · 3h ago
Who runs such an AI generated script without checking the code first?
qwertox · 1h ago
To be fair, the code Gemini outputs in AI Studio is so extremely verbose that it is almost impossible to read through it.
It turns 10 lines of code which is perfectly fine to reason about into 100 lines of unreadable code full of comments and exception handling.
rvz · 3h ago
Recently there was a story about an updater causing a $8,000 bill because there was a lack of basic automated tests to catch the issue. [0]
The big lesson here is that you should actually test the code you write and also write automated tests to check any code generated by an LLM that the code is correct in what it does.
It is also useless to ask another AI to check for mistakes created by another LLM. As you can see in the post, both of them failed to catch the issue.
This why I don't take this hype around 'vibe-coding' seriously since not only it isn't software engineering, it promotes low quality and carelessness over basic testing and dismisses in checking that the software / script works as expected.
Turning $70 problems found in development into $700,000+ costs in production.
I mean, look at the printout. It shows that it created the remote file with the truncated filename, then deletes the local file with the correct filename.
It turns 10 lines of code which is perfectly fine to reason about into 100 lines of unreadable code full of comments and exception handling.
The big lesson here is that you should actually test the code you write and also write automated tests to check any code generated by an LLM that the code is correct in what it does.
It is also useless to ask another AI to check for mistakes created by another LLM. As you can see in the post, both of them failed to catch the issue.
This why I don't take this hype around 'vibe-coding' seriously since not only it isn't software engineering, it promotes low quality and carelessness over basic testing and dismisses in checking that the software / script works as expected.
Turning $70 problems found in development into $700,000+ costs in production.
There are no more excuses in not adding tests.
[0] https://news.ycombinator.com/item?id=43829006