Recent submissions

Comment · 1 month ago
Comment · 1 month ago
Comment · 4 months ago
On the flip side if there is a bug in one of my systems I would rather get a detailed bug report from an llm than a user message “xxx does not work”.
Comment · 4 months ago
This is so obvious that in practice it doesn’t buy much, but everyone is still propagating that silly news. This is the real malware, a mind virus.
Comment · 5 months ago
Comment · 5 months ago
In the limit we want the llm to write the code (like in RLMs).
Comment · 5 months ago
We don’t trust llm execution- so we add user approvals. But task decomposition calls for co-recursion between code and prompts. This means that the approvals should be evocable at any depth. I think we need some kind of protocol for that (à la the Cubes OS protocols for cut and paste between vms).

Maybe a workaround could be to use bubblewrap of the scripts ther recursively call the llm (and run the agent in yolo inside the wrap).

Comment · 6 months ago
The idea is that the spec is somehow compressed in comparison to the code.
Comment · 6 months ago
You need supporting environment on both sides of the sandbox.
Comment · 6 months ago
Frontmatter should now be in the markdown standard.
Comment · 8 months ago
I have been struggling with that. Thanks! Let me reword it - natural language lacks a strict semantics - so also programs for the llm machine ( I.e. prompts) cannot have it. LLMs always have to project from all possible semantics into one (are there any experiments with superpositions?)
Comment · 8 months ago
What is the root cause of this? It is said that AMD is hardware company and neglects software - but recently they issued lots of declarations of becoming software firs now.
Comment · 9 months ago
The point is for the agent to have an index of available skills so that it can decide autonomously if it needs to load one.

https://zzbbyy.substack.com/p/what-are-skills

In my experience it doesn’t work too well with codex, but I expect llm providers to train them on that use case and improve the situation soon.

Comment · 9 months ago
At some point evolving software instead of designing it will work. Now the evolutionary pressure leads towards churning more tokens.
Comment · 10 months ago
Property is a local low - it applies to a thing that exists in one place. Intellectual property is trying to apply similar rules to stuff that happen remotely - a text is not a thing, and controlling copying might work in some technological regimes while in others would require totalitarian control. When you extend these rules to cover not just copying of texts but also at the level of ideas it gets even worse.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton