News for hackers. Stuff that matters.

Creamsicle47

I'm pretty sure thinking is practiced by attempting to argue the opposite viewpoint yourself. Here, you're telling me that you "practice" your thinking by having it actually create the argument for you.

I agree that AI is a useful tool, but it's arguably a very easy tool that people can offload their thought process to - which you should not be doing.

Re:Building an AI-native engineering org on Friday October 30, 2026 @06:59PM (#50311209)
> avoid being subverted in this way

In the instances where they were able to detect it. How much do you think they pour over individual traces nowadays to search for these things?

Re:Building an AI-native engineering org on Friday October 30, 2026 @06:54PM (#50311159)
Even then, the actual development of a harness for interesting problems is a difficult task. It requires more skill & experience than people realize, and gets harder as you scale things up.
Re:Building an AI-native engineering org on Friday October 30, 2026 @06:50PM (#50311124)
Can you please point me to any project based around spec-driven development with agents which has worked well long-term, ideally one that isn't another agentic devleopment tool?
I come from a land down under
Re:US tech stocks see sharp falls over AI cost fears on Friday October 30, 2026 @02:18PM (#50308032)
> Roblox reports user counts are down

Please don't tell me you value your shitty 401k more than keeping kids off of this horrible game

Re:Fixing Tool-Call Accuracy in vLLM on Thursday October 29, 2026 @12:05PM (#50291269)
These edge-cases are why the simplest answer works best: just scale your model to be good enough that it can work through the problem on its own
Re:Zombie stats: Where the numbers AI quotes come from on Thursday October 29, 2026 @12:02PM (#50291214)
Agents in Paris?
Re:Fixing Tool-Call Accuracy in vLLM on Wednesday October 28, 2026 @03:30PM (#50279544)
Technically true, but this is a very inefficient optimization strategy and usually indicates some structural issue with your setup.

When you know enough about the JSON structure to understand how to set a decoding order, then you can simply break the problem into smaller parts so it's more manageable.

Otherwise, you have these solutions: - GEPA-style prompt optimization for simple agents - If working with large models, you can just have them do step-by-step problem solving & relying on their CoT for accuracy. - A small model can simply be trained to do what you want

And if those don't work, I would be extremely surprised.

Re:Mac Studio M5 Ultra 512GB Officially Released on Wednesday October 28, 2026 @02:04PM (#50278179)
As someone also considering getting one, what would make it worth it in your opinion?
It's because LLMs provide an efficient way of optimizing a complex, non-linear search space when there's a way to measure progress. The less verifiable something becomes, the harder it is to optimize (but not impossible).
Re:Fixing Tool-Call Accuracy in vLLM on Monday October 26, 2026 @11:32AM (#50245480)
What the other guy means is the model is forced to decode potentially out of distribution and subsequent parts of the sequence will be sampled from a higher-entropy distribution.

i.e. it might be that a particular model may need some additional conditioning, or perhaps adjusting the order of the json output affects it to produce lower-quality results.

You have to remember that the LLM will be expected to generate 10s of thousands of tokens on a single turn, where things like quantization noise lead to cascading error further on. So when you can, you really want to stay within the model's distribution.

The most sane comment I've seen in this thread
It comes down to the blast radius of a failure happening in your system. Some stateless frontend won't require much beyond visual inspection, but if you introduce some client-server architecture or require payment processing, you must consider the cost of a security intrusion when auditing code changes.
A human acting on inappropriate thoughts can be held accountable in a physical way. An agent producing harmful or dangerous actions will get written off as just a “trajectory that didn’t work correctly”
Re:I know why Mathematicians weep on Thursday October 15, 2026 @01:39PM (#50107226)
"OpenAI is hiring software engineers, therefore all companies will continue to hire engineers"

Generalization fallacy, survivorship bias, etc.

Re:I know why Mathematicians weep on Thursday October 15, 2026 @11:53AM (#50105500)
Holy logical fallacy shit
Re:AI Models Can Provably Hide Arbitrary Capabilities on Wednesday October 14, 2026 @12:13AM (#50082303)
No bro for sure what’s happening is you’re probably fine tuning on some related distribution to the original behavior you are measuring whether it was forgotten.
Re:A misalignment of AI in mathematics on Friday September 11, 2026 @09:20PM (#49667643)
> All of the places facing an unusually high outage rate are places that have seen huge growth in their service usage (Anthropic, GitHub, etc) which is to be expected.

That's not true, many of these outages have been directly attributed to AI tooling.

> The rest of the world has been happily chugging along with coding agents for almost a year now and things seem to still be working just fine.

Many more services are now being attacked by AI agents that originate from all kinds of organizations including OpenAI, Anthropic, and many others. Unless you're purposefully being obtuse, I would not call that "working just fine".

Re:A misalignment of AI in mathematics on Friday September 11, 2026 @06:33PM (#49666299)
> Yet the software industry is plowing ahead, reportedly pushing mountains of unreviewed code to Prod, and the world hasn't ended.

Yes, this has gone so well

Re:Claude Fable 5.1 and Claude Mythos 5.1 on Tuesday September 01, 2026 @03:34PM (#49526939)
The model cannot complete that task, for one reason or another, and therefore it scores lower.
I'd have to push back, though not on the part you'd expect. Your description of human researchers is roughly right: a lot of the field is try-things-and-narrativize-after.

But the load-bearing assumption is that intuition has to be human-shaped intuition. Humans can't intuit thousands of orthogonal directions because we project everything down into a 3D metaphor and hope it holds. That's a fact about our hardware, not about the systems.

And the reason why is the most interesting part: nothing requires the compression step. A model or an agent can operate over the actual objects, holding thousands of runs and ablations in context and noticing regularities in the native dimensionality, without translating them into a picture of a ball rolling down a hill. No bottleneck at "can you visualize it."

So the narrower claim: it's not that intuition here is impossible full-stop, it's that human intuition is unreliable. Your post-hoc rationalization point is evidence for that, not against it. The story exists because a person needs something to hold in their head. Drop that requirement and the failure mode goes with it.

Re:Claude Opus 5 on Friday July 24, 2026 @11:58PM (#49044386)
The user is making an extremely sharp point – full stop.
> You have to look at the size of each expert

Yes, this part is accurate. Expert density determines how much raw compute each hidden state gets.

> The number of the experts tells you about the diversity of its skills.

Most people misunderstand this part. Counter-intuitively experts don't develop diverse skills, they instead balance compute during the forward pass, allowing models to increase their parameter count without the MLP layers exploding in memory + compute requirements.

Re:Lightning Memory-Mapped Database Manager (LMDB) 1.0 on Thursday July 16, 2026 @08:17PM (#48941979)
Don't waste your energy. If you look at the guy's other responses, it will tell you exactly what kind of person you are dealing with.
Re:Kimi K3 is now live on Thursday July 16, 2026 @05:56PM (#48940811)
You mean like Suchir Balaji?
Re:Mesh LLM: distributed AI computing on iroh on Sunday July 12, 2026 @01:28AM (#48878549)
Thanks for answering, that makes sense. Also - your setup seems like it could greatly benefit from speculative decoding. Have you guys given any thought to how that might work in this system?

P.s. for #2, you can probably do something like RAFT-styled interleaved computation. But this could get tricky unless you commit to a sharding scheme that makes it easier.

Re:Mesh LLM: distributed AI computing on iroh on Saturday July 11, 2026 @10:44PM (#48877813)
Hey, this is a super cool project. It's great to see a lot of the IPFS stuff resurfacing again.

A few questions:

1.) How does this handle privacy? If you're distributing compute this way then all actors in the compute graph will also know the sequence being computed.

2.) Any safeguards against malicious actors poisoning model activations?

Re:Mag 7 starting to underperform [pdf] on Monday June 29, 2026 @03:40PM (#48724086)
Ah yes, just what everyone needs: more data centers!
You are stupid

Older »