This is the thing, the LLM has it’s uses and looks like it is year another powerful tool to find vulnerabilities, but vibe coding is just abusing it.
It’s actually kind of crazy if you think about it.
When they specify how the code supposed to be, they want LLM hallucinate everything that they hand waved.
But then at the same time they don’t want hallucinations because those introduce bugs.
I recently saw movement combining TDD and vibe coding, I guess that’s one way that sounds like it might work, but then you are replacing wiring code with wiring code that describes what the code should do.
I’m wondering if that actually is a net positive. I guess for someone who did TDD it is as instead wiring code + test cases they only write test cases. Somehow it reminds me of prolog.
When you TDD, you are supposed to write the minimum possible change that would result in your new test passing. A slop machine is going to try to write code that looks like the end goal of the application you’re writing. Which means it will have tons of untested unexamined side effects.
Also, of course, while you’re human-writing the code for TDD you’re supposed to be thinking about how everything currently works and what edge cases might exist, etc, that is supposed to guide you towards the next best test to write.
What’s the alternative? OpenSpec or something that also won’t solve it? Honestly, this is like when everyone tried to pretend that all bad software must not have been “agile” enough. This shit is going too fast for anyone to understand and it turns out having people slowing down things with padded estimates was helping keep the systems working.
this is like when everyone tried to pretend that all bad software must not have been “agile” enough
Yeah. Nobody who writes complex, critical software uses an agile methodology. There are no databases, no operating systems, no medical devices, no industrial control systems, no large-sale telco code bases that are developed using the agile paradigm.
Agile has a sweet spot, and one attribute of that is that the blast radius is small and the cost of failure low. If you can’t tolerate “fail early, fail often,” you probably need more guardrails. Anyway, agility is a continuum, not an either/or choice.
Its either AI driven patches, or AI driven vulnerabilities wrecking your system. Pick your poison.
This is the thing, the LLM has it’s uses and looks like it is year another powerful tool to find vulnerabilities, but vibe coding is just abusing it.
It’s actually kind of crazy if you think about it.
When they specify how the code supposed to be, they want LLM hallucinate everything that they hand waved.
But then at the same time they don’t want hallucinations because those introduce bugs.
I recently saw movement combining TDD and vibe coding, I guess that’s one way that sounds like it might work, but then you are replacing wiring code with wiring code that describes what the code should do.
I’m wondering if that actually is a net positive. I guess for someone who did TDD it is as instead wiring code + test cases they only write test cases. Somehow it reminds me of prolog.
When you TDD, you are supposed to write the minimum possible change that would result in your new test passing. A slop machine is going to try to write code that looks like the end goal of the application you’re writing. Which means it will have tons of untested unexamined side effects.
Also, of course, while you’re human-writing the code for TDD you’re supposed to be thinking about how everything currently works and what edge cases might exist, etc, that is supposed to guide you towards the next best test to write.
Well, I heard about it but didn’t try, and it sounded plausible.
What you are saying sounds like that’s where the gotcha is.
What’s the alternative? OpenSpec or something that also won’t solve it? Honestly, this is like when everyone tried to pretend that all bad software must not have been “agile” enough. This shit is going too fast for anyone to understand and it turns out having people slowing down things with padded estimates was helping keep the systems working.
Yeah. Nobody who writes complex, critical software uses an agile methodology. There are no databases, no operating systems, no medical devices, no industrial control systems, no large-sale telco code bases that are developed using the agile paradigm.
Agile has a sweet spot, and one attribute of that is that the blast radius is small and the cost of failure low. If you can’t tolerate “fail early, fail often,” you probably need more guardrails. Anyway, agility is a continuum, not an either/or choice.