pull down to refresh

100 sats \ 1 reply \ @optimism 4 Jun \ on: Chorus: An Experiment in Vibe Coding nostr
Since you didn’t write the code, you have no idea what the code is doing
This is perhaps the main obstacle I have in dealing with pull requests from vibe coders.
I was thinking to build something on top of git-diff (on top of clean-code improvements from #997033) where you can tell the vibe coder to just install an MCP tool, where a prompt gets generated to add a comment what this does to each line in the diff that doesn't have a comment what it does.
That way, the LLM gives the user a chance to understand what questions I'm going to ask, and prevent themselves from looking foolish, like "why does this delete 7000 lines from configure.ac?". After all, the vibe coder often has zero knowledge or experience, just "vibes": vibes in, vibes out
write
preview
138 sats \ 0 replies \ @south_korea_ln 4 Jun
Yeah that's what annoys me most too when dealing with junior researchers who suck at coding. They now suddenly come up with long scripts to process data, but when the scripts inevitably fail or produce garbage, they are unable to answer any question i may have when trying to trouble shoot. Debugging vibe code is annoying, debugging someone else's vibe code even more. I told them i don't look at their code anymore unless they can explain each step.
reply