It amazes me how vague I can be in Claude code, and get away with it, with excellent results. It makes me think about how important or unimportant prompting terminology is in app and game development. In your experience, how important is language, really? Can a non-coder who doesn’t know the lexicon of app development get good results out of a frontier model, and how much better is the output of Claude when there’s an expert coder at the helm speaking more specifically? Surely the main job of an LLM is to interpret human language - if you use non-specific word to describe a bug or app feature, the LLM’s job is to filter that and tie this to specific meaning and patterns, to work out what you really mean in the context of the repo. Thus, the very complex set of weights and connections work their miracle of translating human mumbling into a detailed technical plan, where a few basic words can spawn thousands of lines of working code. And yet those who have seen different levels of user vibe-coding, I am fascinated to learn how the LLMs dealt with their input. How much does the quality of code ACTUALLY increase by, depending on the specific terminology of the prompting? Is it significant? Or does the user’s architectural approach matter more than language - as in, knowing where to start, how to iterate on a feature and test at every step, the structure of their use matters more than words? Would love to know your opinion on this. Would like to add also - that it makes me think a lot about IDEs like VSCode and vibe coding tools like Claude. VSCode in particular is very old school now, packed with features no vibe coder will ever touch. What features would benefit a less experienced vibe-coder? Prompt-engineering guidance, tailored to each project? submitted by /u/freedomfromfreedom
Originally posted by u/freedomfromfreedom on r/ClaudeCode
You must log in or # to comment.