Re:Vibe coding creates fatigue?
by QuercusMax on Tuesday December 16, 2025 @04:12PM
(#46294538)
A lot of that stuff can be handled by linters and static analysis tools.
[ Parent
| on HN ]
Re:Vibe coding creates fatigue?
by seattle_spring on Tuesday December 16, 2025 @04:48PM
(#46295015)
What are some examples of linters / static analysis catching hallucinated solutions to problems?
I feel like it would just yield a well-formatted, type safe incorrect solution, which is no better than a tangled mess.
Re:Vibe coding creates fatigue?
by steveklabnik on Tuesday December 16, 2025 @05:07PM
(#46295273)
A specific example: for some reason, when working on Playwright scripts, Claude really likes to inject
await page.waitForLoadState('networkidle');
But this isn't good, and is not encouraged. So much so that there's an eslint that suggests removing it. This means that by running the linter, if Claude does decide to inject this, it gets taken out, because the linter runs and then tells it so.