AI can help you be more agile in getting out a PoC but vibe coding always ends up eating itself and you either aren’t capable enough to fix it (because you are a vibe coder) or you spend more time on the back 9, trying to clean up the code so you don’t have so many hacks and redundancy because the AI was too literal or hallucinated fake libraries that return null or its context window expired and it wrote 5 different versions of the same function
Eh, I’ve enjoyed writing a SQL query and having AI translate it to Linq. I’ve had at least one work directly, very clear on what it’s doing, just with Linq’s odd syntax. The other query was more complicated and wasn’t something that translated well to Linq. I may have had to split that into two Linq queries.
Then again, I wouldn’t count translating psuedocode (or SQL) as really vibe coding. To me “vibe coding” means you’re not really looking at the code it produces.
It’s a changing world, and there is going to be an ever increasing amount of AI slop out there, and even more potential programmers who won’t make the leap due to the crutch.
At the same time, there are always people who want to and will learn in spite of the available crutches the latest tech revolution brings.
There will also be many good engineers who will exploit the tech for all its worth while applying appropriate rigour, increasing their real productivity and value manyfold.
And there will be many non-programmers who can achieve much more in their respective fields, because AI tools can bridge gaps for them.
Hopefully we won’t irreversibly destroy ourselves and our planet while we’re at it. 🙈
AI can help you be more agile in getting out a PoC but vibe coding always ends up eating itself and you either aren’t capable enough to fix it (because you are a vibe coder) or you spend more time on the back 9, trying to clean up the code so you don’t have so many hacks and redundancy because the AI was too literal or hallucinated fake libraries that return null or its context window expired and it wrote 5 different versions of the same function
Eh, I’ve enjoyed writing a SQL query and having AI translate it to Linq. I’ve had at least one work directly, very clear on what it’s doing, just with Linq’s odd syntax. The other query was more complicated and wasn’t something that translated well to Linq. I may have had to split that into two Linq queries.
Then again, I wouldn’t count translating psuedocode (or SQL) as really vibe coding. To me “vibe coding” means you’re not really looking at the code it produces.
It’s a changing world, and there is going to be an ever increasing amount of AI slop out there, and even more potential programmers who won’t make the leap due to the crutch.
At the same time, there are always people who want to and will learn in spite of the available crutches the latest tech revolution brings.
There will also be many good engineers who will exploit the tech for all its worth while applying appropriate rigour, increasing their real productivity and value manyfold.
And there will be many non-programmers who can achieve much more in their respective fields, because AI tools can bridge gaps for them.
Hopefully we won’t irreversibly destroy ourselves and our planet while we’re at it. 🙈