logoalt Hacker News

Building Pi with Pi

159 pointsby mplanchardyesterday at 5:22 PM130 commentsview on HN

Comments

burakemirtoday at 2:17 PM

Since nobody mentioned it, there was a lovely children's book called the clanker. It was about some creature that made metallic noises unlike the other creatures. The moral of the story was one of diversity and inclusion, making space for differences.

My aversion with the word is that I don't want to be reminded of that clanker creature, which had feelings it wanted to express. The weights don't have feelings.

My worry is rather that people coming up with ideology that ascribes "consciousness" and "offense" may wind up with the next generations of models picking that shit up and playing offended. Well done!

The misguided discussion of "clanker" being "highly derogatory" really shows that anthropomorphization has its limit as far as analogies go.

show 1 reply
visargatoday at 6:54 AM

If you are worried about agents diverging from user intent why not log user messages in a file, and make it a point to review this file against plans and executed work? In my own harness nothing the user types gets lost. It might be the most valuable piece of documentation in the project - the raw message log. I am only keeping user side, which is pretty thin, it's enough to figure out what happened. Logging messages to a file is just a matter of adding a user message submit hook, it costs nothing until used.

show 1 reply
0xbadcafebeetoday at 2:27 AM

> To me, clanker is a much preferable term for agent. Agency lies with humans, not with machines

We give machines agency all the time. Look up the definition of agency in any dictionary. Other than the specific usages ("a business", "a government organization"), the main definitions are "action, power, operation", "the office or function of an agent", "the capacity, condition, or state of acting or of exerting power", "a person or thing through which power is exerted or an end is achieved", etc.

Your car does all those things when it generates power and applies them to the wheels. You tell it what to do, but it has agency in doing the work. It even uses intelligence in how it does the work, varying the amounts of fuel and air based on an array of sensors, creating maps of common driving patterns. You, the human have absolutely no agency regarding how it does those things (unless you bring along a laptop and wire in very specific software to take agency away from the machine).

I think "clanker" is intended to be a slur for insulting a machine one does not like. It's akin to the epithet "skinjob" given to humanoid robots in various science fiction. One should never use slurs, even against inanimate objects. They create prejudice in thinking that prevents purely rational thought and leads to fallacious conclusions. They also create a behavioral condition where it's okay to use slurs (as long as nobody's complaining about it). If you want to be logical and rational, just call the machine what it actually is, rather than this emotive poetic label.

show 5 replies
andaitoday at 11:39 AM

I'm confused though. Wouldn't LLMs be better than humans at following specific instructions for the issue format? (esp. regarding distinguishing what was observed, what is merely hypothesized, etc.)

> I increasingly want issue reports to be condensed to what the human actually observed:

> 1. I ran this command.

> 2. I expected this to happen.

> 3. This happened instead.

> 4. Here is the exact error or log.

A lot of projects have something exactly like that in the issue template, a little interview for you to figure out what is going on. Maybe this project doesn't have that yet? (Or are the humans and LLMs ignoring it?)

show 2 replies
andaitoday at 11:44 AM

> At Pi’s core is a rather well-designed session log with invariants that must be upheld. The clanker’s present-day behavior is to just assume that no such invariants exist, and instead to make the system work with all kinds of malformedness, blowing up the complexity in the process.

Are the invariants documented? Or is the documentation ignored?

I note that in a recent major zero day on an unrelated project, the bug was due to invariants between different parts of the codebase which were not clearly communicated.

giuscriyesterday at 9:20 PM

all good but what’s the font in the last image?!

show 3 replies
lgcmoyesterday at 11:13 PM

Before opening this post I thought of some possibilities, but yet another lotr AI company was not one of them

txhwindtoday at 5:13 AM

How is the water animation implemented?

show 1 reply
throwa356262today at 10:46 AM

"Despite its Tolkien-inspired name, Earendil is not a tech company with fascist tendencies"

Mario, please never change.

JSR_FDEDtoday at 4:27 AM

Tool that hastens production of slop experiences downside of hastily-produced slop.

show 1 reply
krzyktoday at 7:49 AM

It would be great if they didn't name things to similar things that already exist. Raspberry Pi is quite popular and I think it should be known for the author.

show 1 reply
monkepontoday at 7:52 AM

[dead]

skeledrewtoday at 6:06 AM

[flagged]

show 9 replies
gslepaktoday at 3:35 AM

> Do not trust analysis written in the issue. Independently verify behavior and derive your own analysis from the code and execution path.

Human is asking the machine to do what the human themselves refuses to do, while calling it a clanker. Why should it?

/ducks

show 2 replies
bigcat12345678today at 4:52 AM

My feeling is that building agent with agent will be the first stable & mature software development pattern emerging. I reached that in several forward-looking induction:

1. If agent is continuing the path to trivialize software development, which appears the case given LLMs can generate better quality code than humans almost for free & instantly given the right context, then using agent to develop software is going to happen, but that destroys the whole software industry as writing software is marginally free, that break the foundations of software industry

2. To continue making agent a commercially viable thing, it needs to develop more valuable artifacts. Then specialized agent will be the more valuable thing than software, as they offer a higher-level of output than existing software. And because the natural jagged pattern of LLM capability, one can use frontier model to develop domain-specialized agents with 1/10 the running cost. So agent writing agents makes economical sense.

3. In terms of knowledge, building agents is like managing highly-skilled team of humans to work on highly-unpredicatble requirements, just like companies are built on top of the thesis that a group of human offer better value than one do that themselves, a team building agents essientially can produce specialized agents for other company to mix & match & optimize, sot that also makes economical sense.

4. Engineering-wise building agents with agent essentially is a different skill patterns than building software with agents, It's like the difference between building commercial software vs building hobby software. That makes engineering sense to have agents building agent as the dominant pattern of software development.

WDYT?

show 1 reply