Have you considered the possibility that, by “finding a bug” and possibly “suggesting” a “patch”, the LLM could be smuggling another bug unbeknownst to the vibe coder(s) and/or smuggling a technical debt?
I say this as someone who’ve been coding since my 8s (now I’m 30), someone who hasn’t the tribalistic anti-AI sentiment (I even use LLMs sometimes, particularly the non-Western ones such as Deepseek and Qwen) but understands LLMs enough to know how the (current, state-of-the-art) stochastic parrots shouldn’t be trusted the source code of any slightly serious project, especially a full browser that Firefox is. Chances are devs are going to blindly trust and obediently stage-and-commit whatever the parroting machine spits out, and this can end up really messy. Given the ongoing pivot to AI from Mozilla, I doubt they’re worried about the consequences of vibe coding, though.
@skarn@discuss.tchncs.de @Solumbran@lemmy.world @linux@lemmy.ml
Have you considered the possibility that, by “finding a bug” and possibly “suggesting” a “patch”, the LLM could be smuggling another bug unbeknownst to the vibe coder(s) and/or smuggling a technical debt?
I say this as someone who’ve been coding since my 8s (now I’m 30), someone who hasn’t the tribalistic anti-AI sentiment (I even use LLMs sometimes, particularly the non-Western ones such as Deepseek and Qwen) but understands LLMs enough to know how the (current, state-of-the-art) stochastic parrots shouldn’t be trusted the source code of any slightly serious project, especially a full browser that Firefox is. Chances are devs are going to blindly trust and obediently stage-and-commit whatever the parroting machine spits out, and this can end up really messy. Given the ongoing pivot to AI from Mozilla, I doubt they’re worried about the consequences of vibe coding, though.
mozilla already said people are doing the fixing afaik, claude only finds them