Live data from Hacker News

Snorting the AGI with Claude Code

kadekillary.work

141–150 of 253 posts

Re: Snorting the AGI with Claude Code

#141

Earlier quoted context omitted.

What??? It’s literally the worst interface Do you not want to edit your code after it’s generated?

I'm running terminal in one window with AI interaction and then VS Code with project on same directories so I can see via color coding updated or new files to review in the IDE. How do you interact with your projects?

I run aider in VSCode terminal so that I can fix smaller lint errors myself without another AI back-and-forth.

Re: Snorting the AGI with Claude Code

#142
post #3

>Claude code feels more powerful than cursor, but why? One of the reasons seems it's ability to be scripted. At the end of the day, cursor is an editor, while claude code is a swiss army knife (on steroids). Agreed, and I find that I use Claude Code on more than traditional code bases. I run it in my Obsidian vault for all kinds of things. I run it to build local custom keyboard bindings with scripts that publish scr…

I had an LLM sort a crap-tonne of my notes into category folders the other day. My god that was helpful

Re: Snorting the AGI with Claude Code

#145
> Is it Shakespeare? No.

It's at least decent though, right?

> "What emerged over these seven days was more than just code..."

Yeesh, ok, but is it accurate?

> Over time this will likely degrade the performance and truthfulness

Sure, but it's cheap right?

> $250 a month.

Well at least it's not horrible for the environment and built on top of massive copyright violations, right?

Right?

Re: Snorting the AGI with Claude Code

#146

Earlier quoted context omitted.

If you can define your problem well then you can write tests up front. An ML person would call tests a "verifier". Verifiers let you pump compute into finding solutions.

Will people be willing to make their full time job writing tests?

We’ll just have an LLM write the tests.

Now we can work on our passion projects and everything will just be LLMs talking to LLMs.

Re: Snorting the AGI with Claude Code

#147
post #127

Earlier quoted context omitted.

I felt the same thing about the onboarding. Like what future are we trying to build for ourselves here, exactly? The kind where instead of sitting down with a coworker to learn about a codebase, instead we get an ai generated PowerPoint to read alone???? Im so over this timeline.

all of this just reads like the supposed UML zeitgeist that was supposed to transform java and eliminate development 20 years ago if this is all ultimately java but with even more steps, its a sign im definitely getting old. it’s just the same pattern of non technical people deceiving themselves into believing they dont need to be technical to build tech and then ultimately resulting in again 10-20 years of re-learni…

20 years before UML/Java it was "4th Generation Languages" that were going to bring "Application Development Without Programmers" to businesses.

https://en.wikipedia.org/wiki/Fourth-generation_programming_...

Re: Snorting the AGI with Claude Code

#148

Earlier quoted context omitted.

Yeah I was done at "What happened here was more than just code..." -_-

You got past the grey text on gray background? -_-

I didn't. I open up Chrome's Developer Tools and drop this into the console:

document.body.style.backgroundColor = "black";

Re: Snorting the AGI with Claude Code

#149
post #22

The terminal really is sort of the perfect interface for an LLM; I wonder whether this approach will become favored over the custom IDE integrations.

sort of, except I think the future of llms will be to to have the llm try 5 separate attempts to create a fix in parallel, since llm time is cheaper than human time... and once you introduce this aspect into the workflow, you'll want to spin up multiple containers, and the benefits of the terminal aren't as strong anymore.

I feel like the better approach would be to throw away PRs when they're bad, edit your prompt, and then let the agent try again using the new prompt. Throwing lots of wasted compute at a problem seems like a luxury take on coding agents, as these agents can be really expensive.

So the process becomes: Read PR -> Find fundamental issues -> Update prompt to guide agent better -> Re-run agent.

Then your job becomes proof-reading and editing specification documents for changes, reviewing the result of the agent trying to implement that spec, and then iterating on it until it is good enough. This comes from the belief that better, more expensive, agents will usually produce better code than 5 cheaper agents running in parallel with some LLM judge to choose between or combine their outputs.

Re: Snorting the AGI with Claude Code

#150

Earlier quoted context omitted.

What??? It’s literally the worst interface Do you not want to edit your code after it’s generated?

...if your IDE doesn't have a terminal then it isn't an IDE.

The "old wisdom" on comp/lang.perl.misc, when new people asked what was the best IDE to Perl programming, was "Unix".

You get both editors to choose from, vi _and_ emacs! All the man pages you could possibly want _and_ perldocs! Of _course_ as a Perl newbie you'll be able to fall back on gdb for complicated debugging where print statements no longer cut it.

Post reply on HN