Live data from Hacker News

Claude wrote a functional NES emulator using my engine's API

carimbo.games

31–40 of 95 posts

Re: Claude wrote a functional NES emulator using my engine's API

#31
post #19
post #13

I'd be curious in how well it passes 100th Coin's NES accuracy tests https://github.com/100thCoin/AccuracyCoin

Indeed, that's what I kind of hinted at in https://news.ycombinator.com/item?id=46442195 and coincidentally https://news.ycombinator.com/item?id=46437688 briefly after, namely that OK, one can "generate" a "solution", that's much easier than before... but until we can verify somehow that it actually does what it say it does (and we know of hallucinations and have no reason to believe this changed) then testing itself…

Isn’t this how all software development works? Folks commit code, it’s tested, and reviewed, and then deployed.

Why would this be any different?

Re: Claude wrote a functional NES emulator using my engine's API

#32
post #15
post #3

It’s a shame that the source code isn’t commented and documented more. At the very least, I would see it being helpful to add some documentation for every CPU op code being emulated.

Forbidding LLM to write comments and docstrings (preferrably enforced by build and commit hook) is one of the best "hacks" for using that thing. LLM cannot help itself but emit poisonous comments.

Or maybe clone the comments from where it cloned the source.

Re: Claude wrote a functional NES emulator using my engine's API

#33
post #5

Git wrote a functional NES emulator for me by simply cloning one of the many publicly available ones!

This is the comment. Give it copy paste / translate tasks and it’s a no brainer (quite literally) But same can be said of humans. The question here is, did it implement it because it read the available online documentation about the NES architecture OR did it just see one too many of such implementations.

> But same can be said of humans.

Indeed, the 'cleanroom' standard always was one team does the RE and writes a spec, another team that has never seen the original (and has written statements with penalty clauses to prove it) then does the re-implementation. If you were to read the implementation, write the spec and then write the re-implementation that would be definitely violating the standard for claiming an original work.

Re: Claude wrote a functional NES emulator using my engine's API

#34
post #14

Who care what it did. What did you learn? To live is to learn.

When I consider the utility of a hammer, my first priority is to ask what the hammer can teach me.

If it's a zillion dollar hammerbot the company is offering to your boss for pennies, that had better be your first priority!

Re: Claude wrote a functional NES emulator using my engine's API

#35
post #20

Earlier quoted context omitted.

There are NES emulators aplenty, the only value in writing a new one is pedagogic, for the writer. This endeavor had negative net value.

How about being entertained by the process?

They didnt call it the "Nintendo Entertainment System" for nothing.

Re: Claude wrote a functional NES emulator using my engine's API

#37
post #24
post #13

I'd be curious in how well it passes 100th Coin's NES accuracy tests https://github.com/100thCoin/AccuracyCoin

I’m sure you can point Claude at that page and have it make the necessary changes to pass.

Or it could loop infinitely, never quite being able to pass all the tests.

Re: Claude wrote a functional NES emulator using my engine's API

#39
post #21
post #17

Earlier quoted context omitted.

to live is to build

Except OP isn't learning or building. He's telling a computer to do the work for him and padding his resume.

How cynical. Just seeing if the current crop of automation systems can do it can be interesting enough for some of us.

Re: Claude wrote a functional NES emulator using my engine's API

#40
post #19

Earlier quoted context omitted.

Indeed, that's what I kind of hinted at in https://news.ycombinator.com/item?id=46442195 and coincidentally https://news.ycombinator.com/item?id=46437688 briefly after, namely that OK, one can "generate" a "solution", that's much easier than before... but until we can verify somehow that it actually does what it say it does (and we know of hallucinations and have no reason to believe this changed) then testing itself…

Isn’t this how all software development works? Folks commit code, it’s tested, and reviewed, and then deployed. Why would this be any different?

That's not how software development works.

Folks think, they write code, they do their own localized evaluation and testing, then they commit and then the rest of the (down|up)stream process begins.

LLM's skip over the "actually verify that the code I just wrote does what I intended it to" step. Granted, most humans don't do this step as thoroughly and carefully as would be desirable (sometimes through laziness, sometimes because of a belief in (down|up)stream testing processes). But LLM's don't do it at all.

Post reply on HN