News for hackers. Stuff that matters.
Re:In 27,280 coding agent runs, 64% of inference spend went ... by Zigurd on Tuesday November 17, 2026 @11:12AM (#50533520)
I find myself pulled in two directions by the performance of coding agents: First, keeping them on a short leash seems sensible. I don't get failed results very often. When I first started using coding agents, this seemed not just sensible but required in order to not deal with a lot of hallucinated weirdness. Secondly though, it's pretty cool to vaguely wave your hands in a certain direction and get both user interface in business logic that's objectively nicer than I would've gotten from the effort I would've put into manually coding. Whenever I cautiously use a coding agent, I wonder what I am missing by not letting it cook.
Re:In 27,280 coding agent runs, 64% of inference spend went ... by embedding-shape on Tuesday November 17, 2026 @11:15AM (#50533575)
Not every problem should (or even could sometimes) be solved the same way. Are you planning to maintain the produced code for more than a year? No, then wave away. But if you're expecting others to depend on it, and you want to be able to continue evolving what it is, then a tight leash and full understanding of how it actually works, is very much needed, even if you don't actually type characters into an editor anymore.

Otherwise you still end up with balls of spaghetti where each change takes longer and longer to work into the codebase. With a bit of planning, you can keep tackling changes and they keep taking the same amount of time more or less.

Re:In 27,280 coding agent runs, 64% of inference spend went ... by smallnamespace on Tuesday November 17, 2026 @11:21AM (#50533689)
[delayed]
Re:In 27,280 coding agent runs, 64% of inference spend went ... by catdog on Tuesday November 17, 2026 @11:31AM (#50533864)
> The cost of AI is rapidly falling while its engineering capabilities keep rising.

Wouldn't count on it. There likely is a ceiling, we might or might not be near it.

Re:In 27,280 coding agent runs, 64% of inference spend went ... by reddit_clone on Tuesday November 17, 2026 @12:48PM (#50535259)
Definitely with the cost. I strongly believe the price now is heavily subsidized and will shoot up in the future. (Not new. First hit is free..)
Re:In 27,280 coding agent runs, 64% of inference spend went ... by datsci_est_2015 on Tuesday November 17, 2026 @11:31AM (#50533882)
Robust systems experience very little turnover in nearly every non-software discipline that involves systems. Why the hell would we insert risk into our system-building processes by needlessly turning over code?
Re:In 27,280 coding agent runs, 64% of inference spend went ... by smallnamespace on Tuesday November 17, 2026 @08:44PM (#50540831)
[delayed]
Re:In 27,280 coding agent runs, 64% of inference spend went ... by Zigurd on Tuesday November 17, 2026 @11:34AM (#50533929)
> The requirements will be more stable than the code.

These kinds of changes to the way teams are formed and managed, and how products are developed is what really fascinates me about the impact of coding agents.

Even if it works, for some definition of works, to dump a huge spec into a coding agent context window, I suspect this is where a lot of horror stories about agentic coding come from.

Teams, and the management structure above them, are going to have to get used to more collaborative and iterative product definition and development in order to extract the most value from coding agents.

Re:In 27,280 coding agent runs, 64% of inference spend went ... by wtch98 on Tuesday November 17, 2026 @11:54AM (#50534320)
> The cost of AI is rapidly falling while its engineering capabilities keep rising. This implies that code is becoming more fungible, and you should expect any code you write today to mostly be replaced in the near future.

I have code I wrote in 2006 which is still in daily use adding business value at my company. Why would it need replacing?

Re:In 27,280 coding agent runs, 64% of inference spend went ... by smallnamespace on Tuesday November 17, 2026 @08:54PM (#50540911)
[delayed]
Re:In 27,280 coding agent runs, 64% of inference spend went ... by wtch98 on Wednesday November 18, 2026 @04:24AM (#50543941)
> One reason is because a lot of older code is insecure

As is a lot of newer code. Depends on the threat model

> Another reason is that if you can find a better way to accomplish the goal, then you should eventually switch to it.

If it's financially better and the gains outweigh the risks, sure

> If your code from 2006 is already perfect and there is no room for improvement

Or more realistically if the cost of improving it would be higher than the business benefit gained from improving it

> which is that any code from 2006 that you’re running has survived the quality filter of time

Not really, it's terrible code. But it does the job, because it was written to solve a business problem, not written to make beautiful code.

Re:In 27,280 coding agent runs, 64% of inference spend went ... by tempfile on Tuesday November 17, 2026 @12:16PM (#50534712)
> This implies that code is becoming more fungible

Code has always been fungible, in the sense that it could be refactored.

> you should expect any code you write today to mostly be replaced in the near future

Why on earth do you think this? It does not follow from your other points. Just because you could turn your business into a rube goldberg code juggling machine, why would you?

Re:In 27,280 coding agent runs, 64% of inference spend went ... by skydhash on Tuesday November 17, 2026 @01:06PM (#50535566)
it's amazing that you could read a book like "The Design and Implementation of the 4.4 BSD Operating Systems" (1996) and still find it relevant to browse the code of OpenBSD and NetBSD, three decades later. While good software gets plenty of updates and additions, the core ideas barely bulge over time. A lot of churn is people playing around with no reason instead of solving the problem properly the first time.
Re:In 27,280 coding agent runs, 64% of inference spend went ... by krrrh on Tuesday November 17, 2026 @12:11PM (#50534628)
A shift is realizing that refactors go from something that was costly and infrequent to something that can happen inexpensively and frequently. It takes some rebalancing.
Re:In 27,280 coding agent runs, 64% of inference spend went ... by rrr_oh_man on Tuesday November 17, 2026 @11:19AM (#50533650)
> objectively nicer than I would've gotten from the effort I would've put into manually coding

I find that only works with topics I know very little about.

Re:In 27,280 coding agent runs, 64% of inference spend went ... by datsci_est_2015 on Tuesday November 17, 2026 @11:29AM (#50533849)
This comment could be interpreted at least two ways, and I’m not sure which it is:

  - tongue in cheek: in topics you know very little about, you don’t have the ability to tell whether the LLM output is trash or not
  - very serious: LLMs allow you to create things you could not have created before due to not having the knowledge
Sort of like a Dunning-Kruger or Gell-Mann amnesia.
Re:In 27,280 coding agent runs, 64% of inference spend went ... by devmor on Tuesday November 17, 2026 @11:38AM (#50534004)
I don't see why both can't be true.

LLMs are allowing people to create things with very little effort compared to before, and those creations are of questionable quality - indeterminable by the LLM-user due to a lack of experience.

Re:In 27,280 coding agent runs, 64% of inference spend went ... by ygjb on Tuesday November 17, 2026 @11:46AM (#50534184)
So, basically, the same as before, but LLMs provide the creations of questionable quality at a faster rate :P

I think the quality of the results vary with the rigor of the process. If you one-shot prompt a new service (even with Fable5) "build me an airtable competitor, no bugs", you will get some real code camp quality results, but a well defined set of prompts and a workflow that leverages multiple coding agents reviewing each others work, and implementing test cases at a relatively granular level yields radically different results.

Couple that with a rigorous design/spec session, and multiple checkpoints (say at release milestone) to monitor drift from the original design makes the process a bit more intentional and measurable, while still being far faster than a typical engineer can build.

Re:In 27,280 coding agent runs, 64% of inference spend went ... by yugoslavia4ever on Tuesday November 17, 2026 @11:55AM (#50534357)
Yes, but before you learned as you went, researching and finding out what good (or at least better) looked like; what learning is done when you wave your hand?
Re:In 27,280 coding agent runs, 64% of inference spend went ... by ygjb on Tuesday November 17, 2026 @10:29PM (#50541493)
Honestly? I have more time to learn now than I did before. I can also do something that was really challenging before LLMs as well, which is turn my lack of comprehension into an demand, guided tour through a Socratic exploration of the unknown topic, including generating labs specific to the skills I want to develop and with the resources I have available.

It's like anything else with LLMs, if you treat it like a magic wand, you haven't really learned or built anything, but using it as a true assistant, it can be a powerful and flexible tool.

Re:In 27,280 coding agent runs, 64% of inference spend went ... by contravariant on Tuesday November 17, 2026 @11:31AM (#50533876)
I think Conway's law applies. In an ideal situation your code mimics your organisational structure.

The places where you let an agent do its thing is bound by the (implicit) interface your prompt creates. In an ideal situation this interface is a simple isolated thing in your application.

If you just let it do its thing, expect a monolith. You shouldn't rely on it coming up with interfaces that mesh well with what you had in mind, and each of those interfaces represents a decision that it took, restricting future iterations of the code. So a monolith is not only what you can expect, but also the best you can hope for.

If you want to let it cook, create more places for code that does a thing and you don't care how.

Re:In 27,280 coding agent runs, 64% of inference spend went ... by Ericson2314 on Tuesday November 17, 2026 @11:34AM (#50533920)
BTW the usual point of Conway's structure is to try to adjust the org / who is working on the software, so you don't get a bad software architecture.

The "objective" nature of code is revealing a flaw in the human division of labor.

Re:In 27,280 coding agent runs, 64% of inference spend went ... by contravariant on Tuesday November 17, 2026 @04:05PM (#50538173)
I think the law is more powerful if you view it as a force of nature. You don't have to make your organisation conform to the shape of the software, you can often do it the other way around.

The trouble starts when the requirements for your software are at odds with the requirements of your organisational structure.

Re:In 27,280 coding agent runs, 64% of inference spend went ... by pjc50 on Tuesday November 17, 2026 @11:43AM (#50534106)
Oh that's a good insight. The agent counts as part of the "organization" for this purpose.
Re:In 27,280 coding agent runs, 64% of inference spend went ... by dcss_gardener on Tuesday November 17, 2026 @01:32PM (#50536011)
You can steer it a lot with implicit context too, like ants following pheromones. If you put an empty docs/ dir in your repo agents will put documentation there without being told. If you put one inline test, they'll write every test inline. If you seed a decision record they'll record their decisions. If you have a lowercase sql query they'll use lowercase sql. If you write a test for wcag AA contrast they'll make ui with wcag AA contrast. And so on.

With some up front care you can create an environment where they mostly do what you want when you let them rip without oversight. As the codebase grows it becomes less likely they'll see any one example, and more rarely expressed ones can get missed. And then codebase predating LLMs or designed without this consideration you just have to accept what you get or wrangle them manually.

Re:In 27,280 coding agent runs, 64% of inference spend went ... by nolok on Tuesday November 17, 2026 @11:53AM (#50534318)
I don't understand why that idea was adopted that IA had to be that "give one command have a perfect run and correct answer" thing when it's clearly not how it works and an eternal "the last % is worth 99%" issue.

I know why the US frontier labs push it of course, you can't push a trillion dollar plus idea if you also say it should be a cheap commodity and the best and latest are now the answer, a bazillion mid levels are.

But most work of value I do is with a swarm of "not the latest nor the brightest" models, with a smart one controlling the dance. Most decisions or review is better done through consensus. The myth that "if we keep going it will reach a point where it's always correct" seems so obvious to me, it doesn't work like that, for that matter we don't work like that.

This is not a jab at it. I work with it. I love it. But I think the story imperative are a mismatch for the actual needs of most companies, and it's hiding between the "frontier needs" of special research & co, or the governemental needs.

On the same line of thought: it's pretty obvious as great as these things are, no they're not going to "replace all employee", and no employee without them won't be able to compete either. They're a supercharger, a self multiplying smart assistant with capabilities in any field, and it feels so wrong to me that they've been presented in a complelty different way.

Re:In 27,280 coding agent runs, 64% of inference spend went ... by wat10000 on Tuesday November 17, 2026 @12:04PM (#50534499)
I recently tried some personal evals to see how some different models performed. I was trying Opus, Sonnet, Gemini 3.8 (this was pre-Argon) and a couple of others. I picked a pull request I'd recently made with heavy Claude assistance, one that seemed simple enough to be quick to solve but with enough subtleties that I could differentiate the results. Set up the agents to run clean without knowledge of the solution, and set them loose.

To my surprise, none of them came close to producing an acceptable PR. Quality varied, but even the very best results were missing significant pieces.

My takeaway is that the human in the loop is still massively important for many things. And that makes it really hard to come up with a useful benchmark.

Re:In 27,280 coding agent runs, 64% of inference spend went ... by krrrh on Tuesday November 17, 2026 @12:06PM (#50534516)
> it doesn't work like that, for that matter we don't work like that.

The parallels with self-driving cars are interesting. We demand that agents don’t just produce better code than most humans (which the frontier models do), but that they perform much much much better.

Re:In 27,280 coding agent runs, 64% of inference spend went ... by sl0wbrainRot on Tuesday November 17, 2026 @02:38PM (#50537010)
Keeping them on a short leash is leetcoding. Handing them one recursive function at a time

Devs are the PMs structuring the sprints now cause they know when/where/how to pivot

See discourse wrt who Nvy should pick as ceo (if JH doesn't come back anyway); at least from what I seen the theme is if they are not an engineer who can keep up with tech and know why Nvidia needs to change course Nvidia is toast

Same with software; everywhere I worked PMs that were not engineers sucked to be at as the PMs Duning-Kruger called the shots not the demands of technical problems before the devs

Re:In 27,280 coding agent runs, 64% of inference spend went ... by Zigurd on Tuesday November 17, 2026 @03:12PM (#50537485)
> Devs are the PMs structuring the sprints now cause they know when/where/how to pivot

You need not just the PMs but the management structure on top of them to get with the idea that product development should be iterative and experimental, not spec driven. But yeah that's how things are going.

Re:In 27,280 coding agent runs, 64% of inference spend went ... by sl0wbrainRot on Tuesday November 17, 2026 @03:42PM (#50537888)
Look at all the small businesses where a sole proprietor and 1-2 others handle it after directly interfacing with their customers which number in the dozens

All those layers appeared in response to ZIRP to fuel job creation. They did not appear out of real necessity and iteration as you call out. You're blithely rattling off a startup spec sheet.

You need that perhaps, or believe you do from extensive prior experience.

2010s are gone; public opinion on such an economy has effectively turned the corner for good.

Same way devs complain about others getting into their flow, computer users at large are tired of a dev riding shotgun, acting like a helicopter parent. They don't want a subscription to you.

A forced obligation of your having reach into their lives while they have no such leverage feels invasive af.