Much better code.

your links don't work

> LLMs are not deterministic

They can be. The cloud-hosted LLMs add a gratuitous randomization step to make the output seem more human. (In vein with the moronic idea of selling LLM's as sci-fi human-like assistants.)

But you don't have to add those randomizations. Nothing much is lost if you don't. (Output from my self-hosted LLM's is deterministic.)

When you say "vibe code" do you mean the true definition of that term, which is to blindly accept any code generated by the AI, see if it works (maybe agent mode does this) and move on to the next feature? Or do you mean prompt driven development, where although you are basically writing none of the code, you are still reading every line and maintain high involvement in the code base?

That's pretty impressive - a genuine real-world use case where the AI is doing the vast majority of the work.

I am considering training a custom Lora on atari roms and see if i could get a working game out of it with the Loras use. The thinking here is that atari, nes, snes, etc... roms are a lot smaller in size then a program that runs natively on whatever os. Lees lines of code to write for the LLM means less chance of a screw up. take the rom, convert it to assembly, perform very detailed captions on the rom and train.... if this works this would enable anyone to create games with one prompt which are a lot higher quality then the stuff being made now and with less complexity. If you made an emulator with the use of an llm, that means it understands assembly well enough so i think there might be hope for this idea.

How would you characterize the overall structural complexity of the project, and degree of novelty compared to other NES emulators Claude may have seen during training ?

I'd be a bit suspect of an LLM getting an emulator right, when all it has to go on is docs and no ability to test (since pass criteria is "behaves same as something you don't have access to")... Did you check to see the degree to which it may have been copying other NES emulators ?

Interesting - thanks! This isn't the type of tech stack where I'd have expected it to do very well, so the fact that you're at least finding it to be productive is encouraging, although the (only) "function level competency" is similar to what I've experienced - enough to not have been encouraged to try anything more complex.

Would you mind sharing what the project is, and which AI you are using? No sign so far of AI's usefulness slowing down as the complexity increases?

There is a better way that I'm using:

1. Cursor Pro with Sonnet to implement things the Cursor way.

2. Install the Gemini Code extension in Cursor.

3. Install the Gemini Coder Connector Chrome extension: https://chromewebstore.google.com/detail/gemini-coder-connec...

4. Get the free aistudio.google.com Gemini API and connect the extensions.

5. Feed your codebase or select files via the Cursor extension and get the implementation from aistudio.google.com.

I prefer having Sonnet implement it via Cursor rather than Gemini because it can automatically go through all the linting/testing loops without my extra input, run the server, and check if there are no errors.

I created a script that merges all files in a directory into this format, and a counterpart that splits it again. Below is just a small sample I asked it to create to show the format, but I did it with almost 80 files including lots of documentation etc.

When providing the flat format it was able to replicate it without much instructions for a blank prompt i had success with the prompt below

===FILE=== Index: 1 Path: src/main/java/com/example/myapp/Greeter.java Length: 151 Content: package com.example.myapp;

public class Greeter { public String getGreeting() { return "Hello from the Greeter class!"; } } ===ENDFILE=== ===FILE=== Index: 2 Path: src/main/java/com/example/myapp/Main.java Length: 222 Content: package com.example.myapp;

public class Main { public static void main(String[] args) { Greeter greeter = new Greeter(); String message = greeter.getGreeting(); System.out.println("Main app says: " + message); } } ===ENDFILE=== ===FILE=== Index: 3 Path: pom.xml Length: 659 Content: <?xml version="1.0" encoding="UTF-8"?> <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"> <modelVersion>4.0.0</modelVersion>

    <groupId>com.example</groupId>
    <artifactId>my-simple-app</artifactId>
    <version>1.0-SNAPSHOT</version>

    <properties>
        <maven.compiler.source>17</maven.compiler.source>
        <maven.compiler.target>17</maven.compiler.target>
        <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
    </properties>

</project> ===ENDFILE===

Prompt to request the format if starting from scratch: Present the entire codebase using the following multi-file format:

The codebase should be presented as a single, monolithic text output. Inside this output, represent each file of the project individually using the following structure:

Start Marker: Each file must begin with the exact line: ===FILE===

Metadata Block: Immediately following the start marker, include these four specific metadata lines, each on its own line:

Index: <N> (where <N> is a sequential integer index for the file, starting from 1).

Path: <path/to/file/filename.ext> (The full relative path of the file from the project's root directory, e.g., index.html, css/style.css, js/script.js, jobs.html, etc.).

Length: <L> (where <L> is the exact character count of the file's content that follows).

Content: (This literal line acts as a separator).

File Content: Immediately after the Content: line, include the entire raw content of the file. Preserve all original line breaks, indentation, and formatting exactly as it should appear in the actual file.

End Marker: Each file's section must end with the exact line: ===ENDFILE===

Ensure all necessary files for the project (HTML, CSS, JS) are included sequentially within the single output block according to this structure.

Crucially, enclose the entire multi-file output, starting from the very first ===FILE=== line down to the very last ===ENDFILE=== line, within a single Markdown fenced code block using exactly five backticks (`````) on the lines immediately before the first ===FILE=== and immediately after the last `===ENDFILE===`. This ensures that any triple backticks (```) within the generated file content are displayed correctly.

If you find youtubers talking about it, they all fully agree that making these thumbnails is soul draining and they are totally aware how stupid they are. But they are also aware that click-through rates fall off a cliff when you don't use them. Humans are mostly dumb, it's up to you if you want to use it to your advantage or to your detriment.

People say his technical opinions can/are bought for the right price or clicks.

vercel shill

Not only actively promotes React which is forgivable, but also every framework or unnecessary piece of npm software that pays him enough.

His videos also have 0 substance and now are mostly article reading, which is also forgivable if you add valuable input but that’s never the case with him.

rejecting an opinion doesn't mean you have to hold the opposite stance, just that their opinion should hold 0 weight.