Plus if the general requirement is ‘high quality code’ then that automatically excludes the majority of LLM usage where people just vibe code it and rely heavily on the LLM to do the work. VS someone writing their own code while using an LLM to help find problems.
Well… IMO, there’s a whole spectrum between “very rare LLM brianstorming/troubleshooting” and “I don’t know how to code” vibe-coding, and Im not sure what the distribution looks like.
Personally, I get LLMs to generate boilerplate, formatting, and functions, but manually write plenty and audit/assemble all the pieces myself. But I would not call myself a vibecoder; I loathe vibe coding.
Yes, that too.
Incentivizing hiding LLM use would be a problem. Encouraging disclosure is good.
Plus if the general requirement is ‘high quality code’ then that automatically excludes the majority of LLM usage where people just vibe code it and rely heavily on the LLM to do the work. VS someone writing their own code while using an LLM to help find problems.
Well… IMO, there’s a whole spectrum between “very rare LLM brianstorming/troubleshooting” and “I don’t know how to code” vibe-coding, and Im not sure what the distribution looks like.
Personally, I get LLMs to generate boilerplate, formatting, and functions, but manually write plenty and audit/assemble all the pieces myself. But I would not call myself a vibecoder; I loathe vibe coding.