My experience, no its not. It just doesn't fight back as much when you tell it that its wrong.
My sister team is vibecoding the shit out of a couple of product PoCs. There is only one person on that team that appears to understand how to vibe code properly. the rest are just producing shite and breaking the service everytime they deploy. However, the code it creates is fine enough, just the architecture is bad, or the prompter is bad.
_however_ the problem with the post is that its using tangential metrics to prove the point. The opensource maintainer bit doesn't always mean that the output is bad, it means that either:
1) the maintainers hate AI
2) the shit they are getting is huge and takes too long to review
3) The shite they are getting solves a specific problem for one user at the expense of everyone else
4) the PR is nonsense.
only one of those options area signal for code quality from LLMs. the rest are about the skill of the creator, or attitude/time budget of the maintainer.
Comments
My experience, no its not. It just doesn't fight back as much when you tell it that its wrong.
My sister team is vibecoding the shit out of a couple of product PoCs. There is only one person on that team that appears to understand how to vibe code properly. the rest are just producing shite and breaking the service everytime they deploy. However, the code it creates is fine enough, just the architecture is bad, or the prompter is bad.
_however_ the problem with the post is that its using tangential metrics to prove the point. The opensource maintainer bit doesn't always mean that the output is bad, it means that either:
1) the maintainers hate AI
2) the shit they are getting is huge and takes too long to review
3) The shite they are getting solves a specific problem for one user at the expense of everyone else
4) the PR is nonsense.
only one of those options area signal for code quality from LLMs. the rest are about the skill of the creator, or attitude/time budget of the maintainer.