Hacker Newsnew | past | comments | ask | show | jobs | submit | calf's commentslogin

Then you're assuming an efficiency that is analogous to how Moore's law made it efficient for chips. Same difference. The problem is that AI scaling in the longest term is a completely unknown problem.

Sounds like safety not for people, but for the technocrats.

Is it certain or all advanced topics? I'm curious if it bans questions about quantum computing or fusion.

Well it's half-and-half, why did Apple struggle for so long with Siri and its pre-LLM era technology, during the time of AlphaGo and so forth, and then after Covid why didn't Apple pivot to something like their own version of Gemini?

But there are lots of differing possible reasons for this, and I think it is premature to conclude with any one in particular.


I'm just a big kid on the inside.

Disagree, someone like the other commenter who points out LLMs don't even understand the domain concepts correctly versus someone who uses it anyways for corporate proprietary results have very different standards for what is acceptable. If you wrangle an LLM with harnesses and clever prompts you could use it to get some amazing results but that has more to do with trial and error and creativity, not some kind of fundamental skill of using LLMs.

It definitely understands the concepts well enough if you give it the right context. I'm not the only one saying this either. Like I said, it's a skill issue.

That's the Clever Hans argument, and the fact that you confidently use this unfalsifiable tactic ("Give it just the right context and it understands stuff!! It works!!" (Well, until the next iteration and then the next until the system paints itself into a corner)) tells me you are engaging in broscience / pseudoscience. Like I say, anti-scientific attitudes like yours are part of the problem, fanning the hype. It's bad faith to attribute people's criticisms of LLMs as some kind of lack of skill. People on here, many who are actual scientists and professional programmers, are very intelligent and highly trained, if they wanted to play around with LLMs they very likely capable of getting impressive one-time results, but proper, sustained use in a non-"vibe-coding" manner, such as with guarantees for validity, consistency, replicability, extensibility, and so forth is a completely open problem. Therefore it is out of proportion to reduce that to human skill. It's analogous to framing a bad design pattern as user error--disingenuous and bad faith. Ironically, with an intellectual standard like that, it then becomes easy to become overconfident about LLMs.

That's amazing, as someone who struggles to find something useful to do with LLMs. How long does this take, several minutes or more? Do you need a paid version of Claude Code for this?

It sat there for about half an hour working out the problem, step by step, before asking me for the preferred solution. At one point, it was trying to decompile the .APK, so I interrupted it and reminded it that Kodi was open source - it was welcome to clone from GitHub.

The only other feedback I gave it mid-process was wrong (I said that the crash probably wasn't caused by cache trimming, it ran some additional tests to confirm that its hunch about cache trimming was right).

This was with the paid version of Claude Code (I don't think they offer a free version at all; that's a Codex thing). The $20 version is as smart as the $200 one, but once you work out it can do stuff like this you'll quickly burn the $20 token limit. :)

The other thing that helps is a CLAUDE.md file - authored of course by Claude itself. Mine's here: https://github.com/EspoTek/.claude/blob/master/CLAUDE.md A lot of it is probably domain-specific for the stuff I do, but the "Working with unfamiliar data or systems" section is bloody gold! Stopped the bullshit completely!


Not the person you were asking but IMHO it all reduces to computational complexity, e.g. biological evolution provided the computational efficiencies that ultimately produced conscious minds and beings, whereas it is not obvious what scale of silicon, power or energy, and input data is sufficient for that to happen artificially. But that means my view is it is a matter of it being possible in principle, merely unknown in practice. Also my view is that denying this amounts to violating the Church Turing thesis of computational equivalence ("human brains are not magic, super-Turing, etc."), and I think a lot of talking-past one another in these public disagreements amounts to one side not actually having taken modern CS theory fundamentals enough to be persuaded of these couple of premises.

That's my take on it too, roughly. I think if we get to trillion-parameter models and they don't exhibit what we'd call AGI, however you define it, then the current transformer based systems never will.

But calling them "unconscious" is a pretty high bar. Mice are conscious. The house sparrow pecking in my yard right now is conscious.


> You want evidence that LLMs are not conscious? Train them on stories where machines say they aren't - they will say they aren't.

That's called brainwashing, and unethical to do on potentially conscious minds... Point being, I don't think it works as the argument you want it o be.


...what do you think an LLM without its training is, exactly?

There's a provocative argument raised in the article that I disagree with:

1. DeepFakes, generative image/video/AlphaFold type AIs are not conscious

2. LLMs are generative AI trained on human text samples

3. LLMs are not conscious, and LLMs just seem-to-be conscious

I might argue instead that (2)-> destroys (1), that in fact we should consider even sensory generative AI are somewhat conscious. That is, Chiang's argument also flows in reverse. Or I might argue text samples (2) are so rich in conscious expression that the same process of training really does produce a conscious machine (through some kind of emergence and complexity.)

Either way his simplistic argument falls apart, and/but the crux of the piece falls on getting basics like this correct.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: