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

Cloudflare, enabling the problem and the solution since, how long has it been?

(checks watch)

17 years

Fun lava lamp story, though


"works" is a loaded term. LFS is how the rubber meets the road, you want how the rubber is made, for that you need something like https://www.baeldung.com/linux/processes-guide or https://linux-kernel-labs.github.io/refs/heads/master/lectur...

And if you want to get to at least the bottom most visible turtle you go with something like NAND to Tetris https://www.nand2tetris.org/

>LFS is how the rubber meets the road

Again I disagree. Way too much time is spent building software than actual practical OS development.


LFS is not OS development. You build a distribution by assembling all the components. If you want to develop an OS from scratch, perhaps you're looking for osdev.org.

What is the point of making a distro, if not to make an OS? It's the same thing.

One supports the other, they aren't laid in opposition, but they are different, well-defined disciplines

When the sole focus is profit and to crush enemies and not to care for the people, the world will start to look like it's full of enemies and profit. It's a self perpetuating, self inflicted situation.

> Meanwhile, I can't even get Astra to consistently re-use the same font-size across all of my HTML page headings+subheadings.

Are you using a consistent or centralised design system across all your projects?


> your prompt is confusing, unfocused, and doesn't work right on any LLM

You are assuming the entirety of the prompt is human prose, but it could be sets of data so the agent doesn't have to collect it every time, like program interfaces, commands, views, databases, tables, data models etc...

I could see this scale to multiple kiltobytes of metadata in the prompt easily.


That usually ends up being a poor use of LLMs, and is an unsolved problem with LLMs.

RAG was supposed to be the way out on that, and ended up being mostly abandoned.


That doesn't make much sense to me because this is in nature much like how harnesses operate: launch a bunch of exploratory subagents to search and retrieve evidence to use in the actual prompt. Think of it as caching this end result so you don't have to re-fetch in the codebase.

That's the other way of doing it, which solves the context rot problem in a more complex way. The model at the top says, "hey, sub-agent, go figure out the answer to this question and give me the answer", and that sub-agent can go consume 250k+ context to return an answer that might be a couple of words, and thus not contaminate the main context with that now thrown-away context.

However, this is not something that is inherently part of models or inference engine, but part of the harness.

Harnesses are very hit and miss, and are not integrated into the stack, and I think that will have to happen eventually. Like, conceptually similar to an LLM performing a tool call that just calls itself recursively, I think this would go a long way to making LLMs more viable for being an actual product people could conceivably want.


You’re right about the harness being the issue. It’s really down to giving it functions specific to your use case that will let it surgically read/modify files, rather than needing to consume entire project folders. I built my own and for Python files some of the most helpful functions I provide are equivalent to:

inspect_function(filename, function, class)

replace_function(<same>)

call_graph(<same>)

And a few other convenient ones. Beyond that it’s trickery like if a function returns more than N lines I omit the result and auto-reply “Your function call was too verbose.” Typically that’s stuff like recursively listing every file in a repo to “see what it’s working with” or similar. When it emits the next call in response to it I clip the previous attempt (and my response) off the conversation and attach the new call/result as if that’s what it did in the first place. I also log that event so if the same type of thing happens often enough I’ll create a special function to address it, or modify an established one so it’s not tempted to do it again.

Language models don’t know what they know, they know what has been said. Even if you give it an entire Python environment it won’t reach for AST, but if you give it a function called Python_AST() it’ll use it every time.

I’ve never seen an off-the-shelf harness that approached it that way.


> that sub-agent can go consume 250k+ context to return an answer that might be a couple of words

How can the parent agent verify the answer without reading some of the context of the sub-agent?


It doesn't have to.

But usually verifying the answer is cheaper than finding the answer, so it can be done. The prompt given to the sub-agent can be a question with "and explain your answer", the answer to which will still consume far less context than figuring out the answer.


> It doesn't have to.

Of course it has to. The subagent might have misunderstood and spent 250k tokens smoking crack. If that output is blindly trusted the parent agent might go on to burn millions of tokens going in the wrong direction, completely negating the point of using a subagent in the first place.


RAG was supposed to be the way out on that, and ended up being mostly abandoned.

Unless you're a contracting agency!


Only if you think in terms of perceived raw intelligence, but self-update is a form of valuable self-improvement that could benefit current models a lot, if they could commit facts from context into their weights cheaply and reliably.

All you can really say is that negligence is corrosive to civilization, and maybe that drugs act as an amplifier of sorts for society's illnesses and qualities.

could also say a corroded civilization makes vulnerable people feel bad and drugs make them feel good

drugs have been making people feel good (and messing with their sense of motivation to behave responsibly) regardless of society's state

That's focusing on low class drug use. Elite drug use leaves a very different trail and has a different impact.

Right, and the elites can deal with it them selves, they have money. They are definitely not directly responsible for the "subterranean environments covered in art and strewn with drug paraphernalia".

Just charge double per view, there will be pressure for competition which is sorely needed in the ads business

It's not solved, I agree. But if we pretend it is we can prepare for when it actually becomes solved, if ever, and measuring sloppiness is a worthy pursuit even if we never "solve code".

  In software development, Linus's law is the assertion that "given enough eyeballs, all bugs are shallow".
In the age of AI, how many eyeballs are traded when choosing generated code over community projects?

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

Search: