41–50 of 95 posts
Earlier quoted context omitted.
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.
Nice, but NES emulator is one of the most written pet projects anywhere, which makes it considerably less impressive.
Heck, when Satya Nadella wanted to demonstrate Copilot coding, he had it emit an Altair emulator. I guess there's little room for creativity in 8-bit emulator design so LLMs can handle them well. https://thenewstack.io/from-basic-to-vibes-microsofts-50-yea...
Until it's so, it's just hearsay to me by someone having a multi-billion horse in the race.
Earlier quoted context omitted.
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, some…
Earlier quoted context omitted.
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, some…
I'm not sure where this idea comes from. Just instruct it to write and run unit tests and document as it goes. All of the ones I've used will happily do so.
You still have to verify that the unit tests are valid, but that's still far less work than skipping them or writing the code/tests yourself.
Who care what it did. What did you learn? To live is to learn.
Earlier quoted context omitted.
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, some…
Earlier quoted context omitted.
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, some…
That's what the author did when they ran it.
Earlier quoted context omitted.
When I consider the utility of a hammer, my first priority is to ask what the hammer can teach me.
There are NES emulators aplenty, the only value in writing a new one is pedagogic, for the writer. This endeavor had negative net value.