I think there are really two types of use cases for LLMs here, and people that get value out of them. First are those that care very little about the quality o

I think there are really two types of use cases for LLMs here, and people that get value out of them. First are those that care very little about the quality of the work, or the process behind it, and just want a 'finished' product no matter what. These are many of the folks vibe-coding everything without even looking at the output, and a depressingly number of those getting hacked or what not. But hey, if you've got an idea for a complex app or website but no interest in actually building it, an LLM will get you... something vaguely like what you wanted. Second are small projects and small sections of existing ones, most of which easily fit inside the LLM's context window. If you're making a fairly basic WordPress plugin or React component or one page website, an LLM will probably be able to handle it just fine. Heck, it might not even look all that different from what a human might have created code wise. One of the big issues we have those is that plenty of people and companies are using these tools despite having requirements that aren't met by them in the slightest. If you're working on a Google/Microsoft/Meta scale product where performance and security and code quality are of the utmost importance, then an LLM isn't going to be a great fit. Unfortunately, that's exactly where this technology is being used, and the results are becoming more and more obvious.