3 ms·
I mean even having linters and everything still creates a whole bunch of noise in their PR section, not to mention that a lot of the changes I make to stuff tha
by sauercrowd 5mo ago
I mean even having linters and everything still creates a whole bunch of noise in their PR section, not to mention that a lot of the changes I make to stuff that's written by codex is not stuff that's caught by linters.
It's just bad/wrong/context lacking decisions and mental models it introduces, that if not carefull will just create a massive mess of a codebase. (I know, because I've tried, and had to deal with it)
And if someone vibecodes a PR and it works, why dont they just share the prompt so a repo owner could vibecode it themselves?
- abustamam 5mo agoVibe coding is often not a single prompt, it's an entire workflow (if you're doing it right).
- sauercrowd 5mo agoDon't disagree, but the "if you're doing it right" is a big asterisk for an open source project with people you have no idea what quality bar they're at. And in my experience it's quite hard to figure that out by quickly looking at it. Not to mention that contributions on github (almost?) never include the prompt chain anyway, so the status quo is even worse
- abustamam 5mo agoThat's a fair point. I was just speaking generally.