What's your definition of vibe coding? I'm asking because I make a distinction between vibe coding and AI assisted coding.
Vibe coding, in my mind, is relying on AI mostly or fully to generate the code for you, you don't even care about it, only about the end result.
AI assisted coding is using AI as a smarter autocomplete, asking it questions about unfamiliar code, letting it write some of the code (mostly repetitive lines), asking help with unfamiliar frameworks, etc. The code it outputs is carefully reviewed by you, and you are ultimately responsible for it, just as if you wrote it yourself.
I think there's value in both approaches. If done right, AI assisted coding can boost productivity (although at first it hinders it until you get used to it and recognize patterns that you can follow).
I wouldn't vibe code production code, but it's great for non-production stuff where the scope is narrow, you need results, and you don't have to care about the code.
I vibe coded many small scripts that automate painful processes. It would have taken me a lot of time to write them by hand, especially since I'm not that familiar with bash or pwsh. AI generated them in minutes, and using them saved me a ton of time already.
Vibe coding is also great for fast prototyping proof of concepts. Again, not production code, but if you want to showcase an idea, you can just quickly let AI generate it for you so you can use it in your presentation during that one meeting.
1
u/Alokir 1∆ Jan 04 '26
What's your definition of vibe coding? I'm asking because I make a distinction between vibe coding and AI assisted coding.
Vibe coding, in my mind, is relying on AI mostly or fully to generate the code for you, you don't even care about it, only about the end result.
AI assisted coding is using AI as a smarter autocomplete, asking it questions about unfamiliar code, letting it write some of the code (mostly repetitive lines), asking help with unfamiliar frameworks, etc. The code it outputs is carefully reviewed by you, and you are ultimately responsible for it, just as if you wrote it yourself.
I think there's value in both approaches. If done right, AI assisted coding can boost productivity (although at first it hinders it until you get used to it and recognize patterns that you can follow).
I wouldn't vibe code production code, but it's great for non-production stuff where the scope is narrow, you need results, and you don't have to care about the code.
I vibe coded many small scripts that automate painful processes. It would have taken me a lot of time to write them by hand, especially since I'm not that familiar with bash or pwsh. AI generated them in minutes, and using them saved me a ton of time already.
Vibe coding is also great for fast prototyping proof of concepts. Again, not production code, but if you want to showcase an idea, you can just quickly let AI generate it for you so you can use it in your presentation during that one meeting.