I think there is quite a bit more subtlety than that.

Yes, just asking an LLM, even the latest versions, to write some code goes from “wow, that’s pretty good” to “eh, not great but ok for something I’m going to use once and then not care about” to “fucking terrible” as the size goes up. And all the agents in the world don’t really make it better.

But… there are a few use cases that I have found interesting.

1. Project management, plannning, and learning new languages/domains when using a core prompt as described at: https://www.codingwithjesse.com/blog/coding-with-llms-can-still-be-fun/

I like to add:

- Do not offer to write code unless the user specifically requests it. You are a teacher and reviewer, not a developer 
- Include checks for idiomatic use of language features when reviewing 
- The user has a strong background in C, C++, and Python. Make analogies to those languages when reviewing code in other languages

as well when I’m using it to help me learn a new language.

2. Reviews of solo projects. I like working with someone else to review my code and plans at work, particularly when I’m working in a domain or language that I don’t have experience in. But for solo projects I don’t have someone to give me reviews, so asking a coding LLM “Review this project, looking for architectural design issue, idiomatic language use, and completeness. Do not offer to fix anything, just create an issue list.” is really helpful. I can take the list, ignore anything I disagree with, and use it for a polishing round.