Typed this up this morning before breakfast. Was thinking how the term "vibe-coder" is thrown around a lot, but I think there's this over-generalization that it means non-coder, or some kind of lazy participant, so I wanted to classify the different type because not all vibe-coders are the same. I'm sure I missed a type or two, but I figured most fit somewhere in this spectrum, but let me know if you're a type that doesn't fit into any of these. I'd put myself in the Architect category. Vibe-Coder Types Observer - You know nothing about coding and ask the LLM to make something for you. No rigid specifications of what you want. You're completely reliant on it from conception to output. Generally happy with whatever you get as long as it works. Muser - You have a rough/general idea of what you're looking for, with minimal instructions. You allow the LLM to build freely, and may include minimal direction. You'll sometimes provide a nudge in a different direction, and mostly get inspired along the process as it evolves, but still heavily rely on the LLM, as you're a non-coder and pretty . Architect - You know very little, if anything, about coding, but spend a lot of time blueprinting the process, and creating full-blown schematics you expect the LLM to follow to the detail. You're constantly involved in the process, ensuring your plans are followed and the LLM doesn't deviate. You adapt when the LLM hits a wall due to bad planning or if you conceptualize an improvement along the way. Savant - You're a coder and give strict instructions to the LLM of what you want, guiding it using supporting documents, targeted instructions, and/or supplementary code. You can review the code and make your own fine-tuned adjustments on-the-fly. You use an LLM strictly as a production tool to speed up production. Grunge   submitted by   /u/GrungeWerX [link]   [comments]