If you are wondering how it could possibly be “worth it” the end of the article has this.
The Fastly survey found that senior developers were twice as likely to put AI-generated code into production compared to junior developers, saying that the technology helped them work faster.
So vibes. Vibe coding is “worth it” because people got good vibes.
If I try to get it to do more than predict the next two lines of code it’s gonna fuck something up. A nervously laughable thing I saw at work was someone using a long spec file to generate a series of other files and getting high praise for it. It was the equivalent of mustache templates but slower and with a 30% chance of spitting out garbage. There was also no way to verify if you were in that 30% zone without looking through the dozens of files it made.
It’ll sometimes do dumb and/or redundant or too complicated shit. Pile up a couple of those and your codebase can get unmaintainable fast.
I find if you give it small chunks and keep an eye on it, it’s great.
I think one of my recent prompts was “Create a procedure that creates an example configuration file with placeholder values. If a config file doesn’t exist on start, give a warning and create the example config.”
You mean rewrite it all from scratch? If you have any kind of standards that is what you end up doing. If you know what you’re doing you do it right the first time and move on. Using AI for coding it like trying to babysit the most inept, inexperienced intern to ever walk the earth. It wastes time and the end result is far worse.
The research shows that - while engineers think AI makes them more about 20% more productive - it actually causes an approximate 20% slow-down.
AI cannot use logic or reason. Everything it outputs is a hallucination, even if it’s sometimes accurate. You cannot trust anything it outputs.
Research shows that - while people think having more people in the household gets the housework done faster - babies actually cause an approximate 100% increase in time spent on housework.
Children cannot use logic or reason. Everything they output is brabbling, even if it sometimes resembles actual works. You cannot trust anything they say. Parents are stupid for having them. (/s)
Developers see AI as a “child” that might need many years to grow up, but it’s still worth all the trouble they go through. It’s an emotional choice, not a rational one.
If you are wondering how it could possibly be “worth it” the end of the article has this.
So vibes. Vibe coding is “worth it” because people got good vibes.
The research shows that - while engineers think AI makes them more about 20% more productive - it actually causes an approximate 20% slow-down.
AI cannot use logic or reason. Everything it outputs is a hallucination, even if it’s sometimes accurate. You cannot trust anything it outputs.
If I try to get it to do more than predict the next two lines of code it’s gonna fuck something up. A nervously laughable thing I saw at work was someone using a long spec file to generate a series of other files and getting high praise for it. It was the equivalent of mustache templates but slower and with a 30% chance of spitting out garbage. There was also no way to verify if you were in that 30% zone without looking through the dozens of files it made.
But surely you test the code and review it, right? That’s how you reinstate trust in what it outputs?
Disclaimer: I’ve never used AI to code, not even copilot.
It’ll sometimes do dumb and/or redundant or too complicated shit. Pile up a couple of those and your codebase can get unmaintainable fast.
I find if you give it small chunks and keep an eye on it, it’s great.
I think one of my recent prompts was “Create a procedure that creates an example configuration file with placeholder values. If a config file doesn’t exist on start, give a warning and create the example config.”
It also works great as a replacement for an ORM.
You mean rewrite it all from scratch? If you have any kind of standards that is what you end up doing. If you know what you’re doing you do it right the first time and move on. Using AI for coding it like trying to babysit the most inept, inexperienced intern to ever walk the earth. It wastes time and the end result is far worse.
That’s what I’m afraid of, and it doesn’t seem like employers are aware of this in general. Irks me especially as a consultant.
Research shows that - while people think having more people in the household gets the housework done faster - babies actually cause an approximate 100% increase in time spent on housework.
Children cannot use logic or reason. Everything they output is brabbling, even if it sometimes resembles actual works. You cannot trust anything they say. Parents are stupid for having them. (/s)
Developers see AI as a “child” that might need many years to grow up, but it’s still worth all the trouble they go through. It’s an emotional choice, not a rational one.