It's another way in which LLMs reflect the misprioritisation in dev learning, itself a reflection of the economic dynamics.. we always focused too much on writing code over reading it, and this production line mentality is why anyone would believe a machine that generates code could replace a developer

We're having to fully articulate the skills in building software for the first time

@sue

This is my confusion when I talk to people who have been "learning vibe coding" I have them describe what they did and it seems they have an LLM write some provisional code for them then they revise it and fine tune it so that it does what they want.

Which is just... coding. Do they think people code without looking at examples, libraries, specifications?

If they don't do that second part then they probably don't have a program that does what they want and they did not do any coding.

@futurebird @sue
I dunno, this actually makes more sense to me than any other description of 'vibe coding' I've heard.

Some people really struggle with "the tyranny of the blank page" and will always start with a template or tutorial even if it has no relevance to what they're trying to accomplish.

@apLundell @sue

Also let's not act like horrible programs that are a bunch of libraries and functions all smashed together by someone who doesn't totally understand what they are doing without regard for elegance or efficiency is anything new. It's just what happens when someone tries to solve a problem with code that's beyond their expertise in programming or experience with those tools. It can also be a step towards learning.