@fasterandworse this is the first thing I thought about when “vibe coding” started getting pushed in our organization. The legacy code this is already creating is enormous. Maybe the thinking is you can just rebuild stuff over and over again from scratch because it’s so fast to do? won’t you eventually completely lose your user base from multiple service interruptions (at a minimum) and catastrophic failures/harm to them (at the worst)?