Trust, but verify. We should always read and understand what gets spit out anyways.
When doing something with any risk potential I first ask the model for potential risks with the output, and then I manually read the code.
I also "recreated" this tool with Sonnet 3.7. The initial bash script worked (but was slow), and after a few iterations we landed on an fclones one-liner. I hadn't heard of fclones before, but works great! Saved a bunch of disk space today.
When doing something with any risk potential I first ask the model for potential risks with the output, and then I manually read the code.
I also "recreated" this tool with Sonnet 3.7. The initial bash script worked (but was slow), and after a few iterations we landed on an fclones one-liner. I hadn't heard of fclones before, but works great! Saved a bunch of disk space today.