Comment by vablings
8 hours ago
That's pretty stupid. Most people who are incurring significant costs are just tokenmaxxing rather than being efficient with usage. You can get 99% of jobs and work done with Haiku/Luna in a collaberating working enviroment.
I feel like people who are later to the AI game just like to "oneshot" and sink a bunch of usage into generating garbage
There really is a skill to using it effectively. I've tried coaching some of the devs on my team. Some get it, some don't.
Our company has been tracking token usage and models used vs output (tickets, story points, PRs, deploys, etc...). A dev got chewed out, even after I warned him, because he spent over $2k in a single month almost exclusively on Opus while his actual productivity in terms of what he delivered was abysmal.
I get it but it goes against the grain for me. Isn't it ironic that we have to waste our precious and expensive human brain cycles to think about how to use AI cheaply so that it is not more expensive than us?
In other words I want to spend 100% of my mental capacity in the problem domain for the things AI cannot do for me, like steering, grounding, verification and not for things AI could do.
> In other words I want to spend 100% of my mental capacity in the problem domain for the things AI cannot do for me, like steering, grounding, verification and not for things AI could do.
It sounds like the parent is less talking about this, and more people burning tokens while not getting useful work done.
I dunno, using tools and resources effectively is arguably the essence of good engineering.
This is much like how devs got grilled for creating expensive test VMs on AWS. Someone has to pay for all this at the end of the day.
What do sorry points mean anymore.
I love the typo.
2 replies →
Did they ever have meaning? It's always been a nebulous feels term
6 replies →
rookie numbers. in one of the top companies, i know someone who tokenmaxed so hard they ended up spending $50000
So you are going to blame this one that dev?
Define productivity, and while at it, quality, maintainability , modularity and so forth.
What are the biggest pitfalls devs on your team fall into?
It's funny, the thing that makes effective prompt also makes effective documentation/communication.
It's bizzare to see people that made clown issues (not enough detail etc.) suddenly start writing detailed prompts just because it is AI that will do the task and not the human on the other side.
The guys that made clown issues are still using AI to make clown issues, they just look like plausible specs now that claude wrote it more thoroughly. At least pre claude I could tell that they had missed something earlier on, ask a question to clarify, and get a real answer they had to type themselves. Now most of my stories are rehashed after I raise PRs or even after these same guys approve the PR and then realize they forgot a requirement.
You mean that now rather than taking 30 seconds to write a ticket, because we all know what we're talking about, we must take 10 minutes to give all the background information to the AI?
there's a manifold to what "effective" means. The problem is once you get into the vibe flow, it's really difficult to eject yourself into the other realms of vscode or IDE or whatever it is you normal do because the vibing provides no anchor to what you're doing.
Even if these models are smart enough to reorient themselves, they get entirely stuck in a desert and now you're asking someone to just pull up stakes and digg them out even thought they only watched them get there and the UI provides so much speed that no human can comprehend how they got there in the first place.
It's like asking a pilot to take over in an emergency situation when they're not tasked with any of the every day requirements of the job. The orgs are relying on borrowed time of experienced professionals, and that's going to erode away and what replaces it is mostly people who understand how to navigate context but not use any of the _classic_ tools.
It's a real conundrum and won't be easily surfaced but for a decade.
I’m trying really hard to keep my skills up but it doesn’t feel productive when I’m using it to write code. It feels like I’m slowing down the AI to the point that it’s not as effective as just letting it go. But I don’t get all the learning that comes from that time along the way.
Have you found ways to stay sharp while using it? Or are you relying on other projects outside of work to keep your skills fresh?
1 reply →
I'm not exactly one-shotting software, but because of the pace I'm expected to keep, I place a lot more trust in the bot that I'm actually comfortable with. I need the job for the time being, so I just keep hitting the button and letting it do its thing until the tests are green.
I'm just working in DevOps though, so it's writing IaC, not application code (save the odd Lambda function or python script). Still, even when I spend an entire day conversing with Claude and watching "bot go brrrrr", I'm one of the lowest users in our company. I have no idea what the devs who regularly hit their limits are doing.
That’s just not how any of this works.
You’re conceptualizing. In reality, AI is expensive, power consuming, planet destroying, and overall productivity killing.
That's what happens when token usage becomes a performance metric. As has been done at my company.
I feel like it's only within the past few months that opus got to the point where guiding the model is faster than doing things myself. I tried out sonnet recently and it was not a net positive to my work. I feel like anything that I'd trust haiku to handle isn't worth doing in the first place.
For context, I'm doing a range of tasks, everything from one-shotting adhoc scripts to having 4 hour 10M+ token conversations debugging things.
That is always amazing to me.
There is no way I can beat even local models at generating complex Python scripts fast.
hn is filled with uber geniuses.
I’m a different person and definitely not a genius but my experience today goes even beyond theirs.
I had Opus trying to simplify a query for me which was slow - it ran for maybe 30 minutes, including writing and running tests, and came up with a refactor across 9 files with a couple hundred lines changed. I was looking through the output before moving onto the next step, and noticed something a little fishy- I said “why does it do x, isn’t that a more complex y?”
Opus thought for another 20-30 seconds then output “Actually that would make the majority of the diff irrelevant, if we do that change it is just these 4 lines in this single file instead.
So then I had it do that. 5-10 minutes of writing and testing and that was done.
So my company spent $25 in tokens and I spent probably an hour in total for a 4 line change that, in the days before Claude, I probably could have found the correct file and thought through the problem, understood the solution, and written the 4 lines of code myself. Probably in the same amount of time.
So basically there was no benefit at all for my time, an extra cost to the company of $25, and now I understand our codebase a little bit less instead of more if I had done all the work.
As good as Claude is at building greenfield projects it still struggles a lot at complex ones
2 replies →
It's not so much that I can code fast, it's that it takes a significant amount of time to tell the model what exactly I want the script to accomplish, and at that point I might as well write the script myself. And often, figuring out what I want the script to do is that hardest part, so it doesn't really matter whether writing the script takes 10% or 20% of the total time.
in my company there are a few who keep sharing screenshots of reaching limits on 3 separate subscriptions, 2 of them their personal on top of the company subscription
Wonder when subscription-hopping attacks will become more often (jumping from a personal model to injecting instructions into the business account and exfiling data)
> You can get 99% of jobs and work done with Haiku/Luna in a collaberating working enviroment.
You can get the same jobs and work done with Kimi and GLM (ZDR on OpenRouter) for a fraction of the price too.
Sorry, but that is nonsense. Compared to opus haiku doesn't cut it most of the time.
I think they mean the new Haiku, which is mildly above Luna now . If you have a plan written by a smarter model (so the hard parts are solved) they can be great at implementation.
I use Qwen3.8-27B as a daily driver, and for things I know will be quite hard I tend to get ChatGPT to do the planning. Works very well.
1 reply →
What on earth do you even do with these models?
Or does a "collaborating work environment" mean that everything is basically spoonfed to them? Or do you only ever use ghost suggestions?
I genuinely cannot even fathom. Just how do you even get into a state where tasks are so clear and cookie cutter? These things are abhorrent. Not only are they not useful, it's an outright form of psychological torture to try and use them. They almost fight you.
Luna doesn't even respond to steers properly! You try steering it and it immediately gets distracted and then just stops.
I can imagine coercing Sonnet into doing some of my tasks okay, but Haiku? Especially 4.5? Really?
I think you might be overestimating the sort of projects most of us have worked on throughout our careers -- we haven't been doing much groundbreaking work. LLMs can easily and successfully write most code.
I equate most LLM work to squeezing a glue bottle
It's just glue code
It's not complicated. Someone just has to be there to squeeze the bottle
It's possible it's my role distorting my perception, cause technically I don't write software, I work an SRE role. None of my items come pre-chewed or paced, it's all good luck and god bless.
I'm desperately trying to classify and standardize my work items and delegate them to less capable models, because my usage is clearly unsustainable and this same sentiment as above keeps being pushed on me too. But all my tasks are genuinely fairly arbitrary, so there's no real way around the agent actually being able to reason about business and technical context proper. It's not even that they're hard, it's just that they're dynamic.
I can get Luna to do things like walk our observability stack and perform a healthcheck, then defer to a stronger model if anything looks super off, but if I'm being entirely honest, this could basically be just a script. Which Opus 5.5 will immediately write for itself if it doesn't yet exist, run that, and then off it goes depending. But Luna will never actually do an investigation proper. Heck, it can't even read our dashboards most of the time, tripping up on Grafana minutia.
It feels like that surgeon vs surgeon comparison, where you're made to decide based on their surgery success rate, and the better succeeding surgeon simply reward hacks the number by only operating on less dicey cases. Except there's no objective way to make this classification here, so jackasses like the above get to play with my insecurities with full obnoxious confidence, while I'm left desperately trying to slim my usage and failing to do so between two moments of crippling self doubt and blockers.
3 replies →
> You can get 99% of jobs and work done with Haiku/Luna in a collaberating working enviroment.
Optimally? Opus will pay for itself if you save just 10% of your time
Only if all money is equal. Budgets in big enterprises work differently.
True. I always Opus to pay for itself if it wants to get used by me.
the poster did mention "if it saves 10% of your time".
So be less snarky?