Taran Rampersad
Thomas ◉ small batchesVibe Coding is just Waterfall with better marketing.
You specify upfront, let the machine run for hours, come back to check what came out. Sound familiar?
The feedback loop is still missing. The waste is still there. It's just faster waste.
@nobsagile the only thing that changed was everyone got a team to run and adds little themselves. 😃
Great point!
SCRUMschauI do not get it..... Is Vibe Coding a big one time shot? And not a "I have an idea, do it" - "I do not like it, do that better" - "nice. Can you had this?" - "another color please".
@scrumschau "Vibe coding is a software development practice assisted by artificial intelligence (AI) where the software developer describes a project or task in a prompt to a large language model (LLM), which generates source code automatically. Vibe coding may involve accepting AI-generated code without thorough review of the output, instead relying on results and follow-up prompts to guide changes."
@scrumschau Karpathy had something in his mind when he startet to use "Vibe".
"fully give in to the vibes, embrace exponentials, and forget that the code even exists".
This leads to long prompts and more frameworks like https://github.com/obra/superpowers that all try to develop something over hours/days without human interaction with the promise that you get a running product (... to sell)
@scrumschau Often enough people argue that that is fine and that they have TDD and so on. But: what is TDD? Architecture and thinking. What are LLMs not capable of? Architecture and Thinking. You see where this goes?
Reinald Kirchner@nobsagile @scrumschau I had a thought about this "I don't even check the generated code any more" thing... looking for an analogy.
When I have a CNC machine, and produce tiny boxes to sell on etsy, I just run the machine. No reason for checking the measurements. Tool wear, machine slack, does not matter.
When I have a CNC machine, and produce turbine blades for an aircraft to spin at 120k rpm, I am well advised, to do quality control on each and every part. Even though I repeat the program
@nobsagile @scrumschau in a similar way.
It depends a lot, what depends on your product. When your life depends on it, you might have a different level on attention to detail, as if it is just entertainment purposes.
@nobsagile @scrumschau
We often don't understand the impact of software completely - it might create ripples 2nd and 3rd order that we didn't even think of in our wildest dreams. And so can bugs, glitches, sloppy designs impact more than we think.
NOT checking code, NOT even trying to understand code is definitely sloppy IMHO. Might be okayish for a prototype. But is grossly negligent for a public release.
We often don't understand the impact of software completely - it might create ripples 2nd and 3rd order that we didn't even think of in our wildest dreams. And so can bugs, glitches, sloppy designs impact more than we think.
NOT checking code, NOT even trying to understand code is definitely sloppy IMHO. Might be okayish for a prototype. But is grossly negligent for a public release.
@Reinald @scrumschau or for a tool one only uses for himself
@nobsagile @scrumschau What depends on it? Even if you are the ony user of a tool, your decisions based on that data you compiled might impact others. A report or a dashboard, that slowly creeps away and leads to wrong conclusions.
Effects higher order might appear at unexpected places and through unexpected connections.
Effects higher order might appear at unexpected places and through unexpected connections.
@Reinald @scrumschau True - I meant a tool that is only for me...
@nobsagile @scrumschau even if - you are not living in isolation.
Interview with Vibe Coder in 2025
@scrumschau LOVE the channel :)