There’s an anecdote that comes up in software about people working on missile software not caring about memory leaks because it’s going to explode anyway before that becomes an issue.
Who cares about bugs in your software if it’s a hobby project that’s going to blow up anyway.
Also, including Claude doesn’t inherently mean vibe coded, it can be for writing tests, small components, or debugging.
There’s nothing inherent to small components to suggest that you have to review them. If they’re small, it’s easier to tell yourself that the LLM probably got them right and you’re justified in not checking.
There’s an anecdote that comes up in software about people working on missile software not caring about memory leaks because it’s going to explode anyway before that becomes an issue.
Who cares about bugs in your software if it’s a hobby project that’s going to blow up anyway.
Also, including Claude doesn’t inherently mean vibe coded, it can be for writing tests, small components, or debugging.
Using an LLM to write tests and small components is still vibe coding.
Wikipedia says:
If you are using LLMs to write e.g. small components, then you are typically understanding the structure of the program, and reviewing it.
There’s nothing inherent to small components to suggest that you have to review them. If they’re small, it’s easier to tell yourself that the LLM probably got them right and you’re justified in not checking.
Listen to me. I do code for a living. Nobody want to write HTML