Post BA1NaJz13W0hKXUY0O by agowa338@chaos.social
(DIR) More posts by agowa338@chaos.social
(DIR) Post #BA1LNKaDJWmLWBZJiq by ariadne@social.treehouse.systems
0 likes, 0 repeats
honestly I do not even understand how the vibe coders keep rm -rf'ing themselves with their bots, like it does not make sense to me how that could happen on its own unless they are literally YOLOing it
(DIR) Post #BA1LguateMf8hrE0Ke by agowa338@chaos.social
0 likes, 0 repeats
@ariadne Well these tools condition you into trusting them as they kinda "just work". However they're also still unreliable in nature.Like the last "rm -rf"-ing I encountered was hidden in a unit test the slop machine wrote. The task was to basically clean up /tmp in a safe way and "don't delete anything else".So what did the slopmachine do to ensure that in the unit test? Well it tried to delete /home. And the code failed the check...
(DIR) Post #BA1N2UTzVoC033qf0i by ariadne@social.treehouse.systems
0 likes, 0 repeats
@agowa338 I would just design things where that could not be a hazard... humans win again
(DIR) Post #BA1NAhzp9Z5wHBelnM by ariadne@social.treehouse.systems
0 likes, 0 repeats
@agowa338 @ChrisUplus exactly
(DIR) Post #BA1NXEODOc5H75nxcu by jamesh@aus.social
0 likes, 0 repeats
@ariadne I think a lot of it is permission prompt fatigue. You either run the tool in an "present so many permission prompts the user stops reading them" mode, or run in the "say yes to everything" mode.It works for transferring blame from the creators of the tool, but doesn't really help with the user making informed decisions.
(DIR) Post #BA1NaJz13W0hKXUY0O by agowa338@chaos.social
0 likes, 0 repeats
@ariadne But then you run into confirmation-fatigue and end up with the human just blindly hitting "confirm" as most of the time it is just doing its thing. That's exactly what I meant with "causes you to let your guards down".