Vibe coding: massive tech debt generator?
Why all the hate for agile? Is it like democracy? Maybe it's terrible, but all the other options are worse?
The key is short feedback loops so you can get the maximum information so you can bet your resources accordingly. I don't think enough is made of the fact Kent Beck likes to play poker. Agile is not supposed to be exactly like poker (internally, at least), but the principle is that you have a hand and you make your bet based on how strong you think your hand is. Agile is meant to turn ideas into software that gets used as quickly as possible. How much do you need to bet today, next week, next month in order to achieve your goals? How quickly can you learn from your experience to change your behaviour today, next week, next month to achieve your goals more efficiently? Do you need to reduce your bets, do you need to increase them?
My worry with vibe coding is that it can create too many changes at once so you don't learn what really worked and what didn't so you get a false idea of what to do next. TDD can seem slow at first, but ideally you only change one thing at a time so you know exactly what worked and what didn't.
Nothing wrong with vibe-coding a small tool or web interface for something that you know won't need to change much, but instead of building massive tech debt over years you could end up amassing enormous tech debt in minutes.