cloudhead

@cloudhead.io

Computers, graphics, protocols. Working on @radiant.computer Previously @radicle.xyz

I think Fable 5 / GPT 5.6 write better code than the average open source developer now. My reaction to seeing an AI-generated OSS repo is starting to go from negative to neutral.

It would be cool if you could rebase a conversation with an LLM after editing one of the earlier prompts. Just like `git-rebase`, but over a chat log. This would allow edits to trickle down to all subsequent responses.

The major downside of vibe coding is that you end up with 1) much more code, and 2) badly factored code, which leads to 3) very poor token efficiency when making changes. It probably still all works, but the cost of maintenance and change grows much faster than for manually written/reviewed code.

user> just fix all the bugs I'm tired and going to bed. llm> ok, I'll fix all the bugs. ... 8 hours later ... llm> Wait, the issue might be... Actually... blah blah llm> But wait! Let me just.. blah blah blah user> I'm going back to bed.

1. Writing a compiler in C to compile Radiance to RV64 ✅ 2. Porting the C compiler in (1) to Radiance ✅ 3. Compiling the ported compiler in (2) with the compiler in (1) ✅ 4. Compiling the self-hosting Radiance compiler (3) with itself 💥😵‍💫

I've been in the deep end on the Radiance AST -> IR lowering pass, but I'm starting to see the light of day. I did things a bit differently this time in terms of code production, and I'm not sure it was worth it: I had Claude generate this compiler pass from scratch, which resulted in...

One of the greatest skills in software engineering is to know how much code is needed to implement any given feature. This lets you immediately tell, without reading the code, whether it doesn't account for something (code too short), or it's overcomplicating the solution (code too long).