Yes. Except that cursor is running at a loss and so is the company running the LLM that they pass all the work on to.

Variable rewards is a very good way to get people (and animals) addicted. Vibe coding happens to operate in that area.

first line in any AI prompt: "do not comment on the quality of my questions"

I imagine that it is theoretically possible to successfully vibe-code, but probably not with a conventional project layout nor would it look much like traditional programming. Something like your interaction primarily being a "requirements list", which gets translated into interfaces and heavy requirements tests against those interfaces, and each implementation file being disposable (regenerated) & super-self-contained, and only being able to "save" (or commit) implementations that pass the tests.

...and if you are building a webapp, it would not be able to touch the API layer except through operational transforms (which trigger new [major] version numbers]. Sorta like MCP.

Said another way, if we could make it more like a "ratchet" incrementing, and less like an out-of-control aircraft.... then maybe?!?

When did Rick Ruben become a vibe coder?

After using opencode.ai to create some python apps and a webui, when you ask to do something you don't know if it will fix it or break everything

Recently I roo-coded a node.js MVP without knowing too much about Node, but something about JS/CSS/HTML although it's years ago I last used it.

I got something working decently by:

• Make a project plan and use cases
• Take (very) small steps
• Commit often
• Throw away bad attempts
• Make test cases
• Hand edit from time to time, especially CSS stuff.

Would I have been able to fling something together by reading some node.js guides and using stack overflow yes, would it have taken around the same time yes, but without test cases and documentation. Do I think vibe coding is the best thing since sliced bread no!

The very first comparison fails, though. I run LLMs locally on my own computer, tokens cost me nothing.