3 ms·
This is as naive as you’re arguing the parent is. I agree you need to care about customers first, and make sure you’re solving their problem, but you absolutely
by yladiz 1y ago
This is as naive as you’re arguing the parent is. I agree you need to care about customers first, and make sure you’re solving their problem, but you absolutely do need to care about the code and if you treat it as always throwaway you can logically get to a justification for vibe coding. Of course you can get far witn these approaches, but they lead to unmaintainable messes which ultimately make it hard or impossible to actually do the thing you want: to deliver customer value.
- makeitdouble 1y agoI'd argue if you care about your customers, vibe coding will be a no-go. Most of us aren't against it not on principle, but because it's just too risky or too inefficient to bring real value in most applications. If someday it produces messy but actually reliable code my opinion will change, but at this point, it's just too early (not saying it will ever work, but one can hope)