I understand the audience this person has written for: professional developers. In that context, sure. But for everyone except professional developers vibe coding is amazing.
It gets the things they want to do done. No paying someone else, no asking for help on $chatprotocolchannel, no getting a friend to help. It's just there. It doesn't matter if it's ugly. It doesn't need to be monetized, doesn't need to be worked on by a team of people. It just needs to work... enough.
Vibe coding may not be for you. But vibe coding is so that we don't need to bother you for trivial things (like porting a 12 .c file X11/cairo program to a single .pl file cariro/gtk program).
Even for professional developers I am not buying this argument. I think there is an argument to be made that we actually don't know how to work with these tools effectively and repeatably yet. But as the tools improve and we figure out the processes more that may change. It might not too, but I am leaning more toward it working better when we figure out how to use it than not.
e: Not a q for parent, but maybe for others. Are we supposed to be making a distinction between "vibe coding" and "coding with an AI agent"? What is the difference?
That may be true (although I doubt the numbers add up). But what is keeping those researchers from walking away, or underperform whenever they feel like it? Giving them a lot of money surely isn't going to motivate them to work harder.
It's probably giving them access to one of the world's largest clusters of compute that lures them in.
isnt that the reason we give ceos lots of money?