121–130 of 489 posts
My experience is, Claude Code burns way more tokens compared to other agents, probably to ensure high levels of perceived quality, which is, most of the times not worth the bloat for the user. The bloat works for Anthropic as an advertisement at the cost of your tokens.
Surely a company as large as Microsoft is actively attempting to build their own models. They couldn't possibly have expected to stake the future of their software development on the conditions of a third party company?
Curb Your Enthusiasm theme starts playing .
Earlier quoted context omitted.
There is always a quantity of lubricant that can get any machine moving. Just add so much that you create an all consuming river of lube and watch your thing sail away.
Good then that Amazon sells it by the 55 gal drum then. https://www.amazon.com/Passion-Lubes-Natural-Water-Based-Lub... > This product is out of stock Ah, shoot, there go my weekend plans. Bummer.
There's definitely a way to use Claude code that is token conscious. I've tried throwing unsupervised agentic software factory workflows against the wall, and they burned through my tokens like nobody's business but didn't produce much. Supervised, human-in-the-loop process on the other hand is much more productive but doesn't consume nearly as much. Maybe that's why everyone's pushing agentic approaches so much.
At the enterprise level though, its going to be hard to want to use a service in which costs are not predictable, and keeping those costs under control requires employee training.
Isn't this a (mildly exaggerated) description of AWS, which is a very successful service?
Earlier quoted context omitted.
I suspect subscription limits are quite a bit higher than the equivalent tokens their dollar cost could purchase. I similarly feel like I can get a lot done with a $20/mo Claude Pro subscriptions, but also can easily spend $10-20/day at API pricing with similar usage.
I don't understand why people are using the API pricing instead of the Pro/Max subscriptions? What am I missing?
Earlier quoted context omitted.
I suspect AI would have to get drastically more expensive before it starts looking worse than payroll. If one developer using Claude Code can effectively substitute for 2 developers, you are already coming out ahead at current API pricing assuming very heavy usage, your cost is going to be ~1.5x developer (factoring in beyond salary - benefits, PTO, the other overhead that comes with having employees). So you're gett…
You're starting from the assumption that its a 2x benefit. That's a massive leap.
Earlier quoted context omitted.
I rage canceled Claude today. After 2 weeks of Claude getting progressively worse and worse, today was the final straw. I don't care if they have a phone app. The model is COMPLETE garbage after you subscribe long enough and they think they've "got you". I can't code on my phone if the model literally moves in the wrong direction and does the opposite of what I tell it to. If I wanted to make my code worse, I'd just…
I've seen a lot of this sentiment over the previous six months from people on reddit. I have yet to experience this myself as a developer with over 20 years of experience.
Earlier quoted context omitted.
I don't understand why people are using the API pricing instead of the Pro/Max subscriptions? What am I missing?
Personally I prefer the API pricing because I feel like I'm not going to get rug pulled on my work. When it comes to personal stuff, I use the shit out of my sub, but it's not making me money.
There's definitely a way to use Claude code that is token conscious. I've tried throwing unsupervised agentic software factory workflows against the wall, and they burned through my tokens like nobody's business but didn't produce much. Supervised, human-in-the-loop process on the other hand is much more productive but doesn't consume nearly as much. Maybe that's why everyone's pushing agentic approaches so much.
At the enterprise level though, its going to be hard to want to use a service in which costs are not predictable, and keeping those costs under control requires employee training.
Like the other commenter said: cloud spend can also spin out of control if you don't pay attention, yet we've found ways to keep it under control (training, guardrails, limits, transparancy).