pull down to refresh
130 sats \ 3 replies \ @optimism 4 Sep \ parent \ on: Brian Armstrong says about 40% of Coinbase’s daily code is AI-generated AI
So we've come to basically 3 variations:
- AI-assisted completion
- AI-assisted coding (you're more likely to understand what you're coding here)
- Vibe coding
I fully agree that completion is sustainable and the second variation, assisted coding, isn't much different from someone doing C&P from stackexchange, perhaps even a little more advanced even, so that's manageable; but it could still be debt, especially when refactoring. I must admit that I really like the "let's discuss this code" use-case. This is much better than having to browse reference sites and a great improvement when you're learning (which you always are.)
Vibe coding currently isn't practical for anything past prototyping and those are throwaway prototypes at that. Anything complex that for example needs concurrency control is in my experience until now problematic for LLMs, including Claude 3.7 and 4, and Qwen3 coder. I think this is also risky with #2.
I think vibe coding has its use cases. As a teacher, I've always wanted to come up with these little interactive examples. Vibe coding makes it way faster to do that. In fact, that single page static website I mentioned was exactly such a use case. But you're right, for larger projects it's nowhere near "there" yet.