This is an obvious mistake, the price is per Megatoken, not per token.
Is it really vibe coding if you are building a detailed coding plan, conducting "git-based experimentation with ruthless pruning", and essentially reviewing the code incrementally for correctness and conciseness? Sure, it's a process dependent on AI, but it's very far from nearly "forget[ing] that the code even exists".
That all said, I do think the article captures some of the current cost/quality dilemmas. I wouldn't jump to conclusions that these incentives are actually driving most current training decisions, but it's an interesting area to highlight.
[1] https://trends.google.com/trends/explore?geo=US&q=%22vibe%20...
https://www.microsoft.com/en-us/worklab/why-using-a-polite-t...
It has a very good system prompt so the code is pretty good without a lot of fluff.
Clearly something like “server telemetry” is the datacenter’s “CRUD app” analogue.
It’s a solved problem that largely requires rtfm and rote execution of well worn patterns in code structure.
Please stick to the comment guidelines:
> Please respond to the strongest plausible interpretation of what someone says, not a weaker one that's easier to criticize. Assume good faith.