Post

This is where my opinion has landed as well. Most of the “typing” is done by LLMs for my own code these days, but I’m still in my IDE, reading, watching the diffs go by, interrupting to tell it to do something differently, refactoring regularly to make sure the code is legible.

Have you used Codex for the 'steering' angle? It reads your message while continuing, whereas claude you have to explicitly stop it, or it waits for some kind of gap to actually read your message. The message queueing in claude code just feels bad in general now

I too also went a bit over the deep end, with the point at which I first read the code being a (draft) PR, and honestly it was kinda cool at first but I'm now back to either babysitting or heavily scrutinising and iterating on a plan before starting to execute.

This is on Monzo's big and complex systems though, very different approach when doing something for a personal project.

In terms of the actual output, not sure - can’t use codex at work at the moment. Feels like a nicer ux, I message now and it sees it now. With claude often I’d message and then mid typing be interrupted by a command approval prompt. With interrupting I worry about the timing being bad?

In what way could the timing be bad? I tend to interrupt then type, because if I type sometimes it’ll make a bunch of changes I knew I didn’t want.