I can taste the difference between a $100 wine and $400 wine, but it's maybe 20% better, if it's possible to flatten extra layers of flavour into a linear scale. It's easier to appreciate for different levels of quality from the same producer. My example is drawn from Casanova di Neri Tenuta Nuova vs Cerretalto. They're basically the same style, the Cerretalto just has extra.
Across different grapes and regions and it's like apples and oranges. Sometimes I want a savory Burgundy, sometimes I want a Coke. If you don't know what wine from a terroir tastes like, and hankering after that, don't spend extra on it.
I'd generalize that to cheese. Can't beat a good aged Comte (a raw milk cheese), but it's not everyday cheese.
Right, this is a car-priced CPU and the only rational reason to have one is that you can exploit it for profit. One pretty great reason would be giving it to your expensive software developers so they don't sit there waiting on compilers.
I always tell Claude, choose your own stack but no node_modules.
What's missing is another LLM dialog between you and Claude. One that figures out your priorities, your non-functional requirements, and instructs Claude appropriately.
This perhaps reflects the general divide in viewpoints on “vibe-coding”. Do you let go of everything (including understanding) and let it rip, or require control and standards to some degree. Current coding agents seem to promote the former. The only way with their approach, is to provide them with constraints?
> What's missing is another LLM dialog between you and Claude. One that figures out your priorities, your non-functional requirements, and instructs Claude appropriately.
There are already spec frameworks that do precisely this. I've been using BMAD for planning and speccing out something fairly elaborate, and it's been a blast.
An opinion that formed after the war, but not actually anchored in reality. None of the elite really wanted a war, some levels of the military did. Nicolas II raged against his generals that he did not want to mobilize and send men to their deaths. The German leadership didn't want a war, they thought it was inevitable but that they'd lose. The Austro-Hungarians definitely didn't want a war with Russia but did want to give the Serbs a black eye for the assassination in Sarajevo, and made a number of bad decisions. The British tried to stop the war and a number of politicians there wrote about the potential consequences before it happened.
In a way it's sadder than other conflicts: none of the participants entered the war for power or control, they all thought they were defending themselves. Plenty of people knew the human cost would be high. Events and fear and lack of fast communication just took over. And it set up the conditions for WW2 and probably the cold war.
$50 will last you a good long time if you don't use many tokens, and you are judicious about which model you use, and don't need web search much.
However, on a fixed price plan your behavior changes. It's a qualitative change in how you work, rather than quantitative. Ideation and product design and specification start becoming bottlenecks.
I started out the API route. I started spending $100 a month once I was spending upawards of $10 in tokens a session.
A sufficiently detailed spec need only concern itself with essential complexity.
Applications are chock-full of accidental complexity.
reply