It's interesting how predictable some of this is.

The LLMs turn out fully formed clones of stuff for which there exists copious amounts of code openly searchable on the web doing the exact same thing.

LLMs require developer-like specification, task/subtask breakdown and detail where such example code already exists.

As a professional prior to LLMs, how many problems that you work on have many existing free solutions but you neglected to use that code and decided to spend days doing it yourself?

▲

bonesss 3 hours ago | parent | next [-]

Well put, and same challenge to a lot of these demos & LoC numbers: if you were a pro prior to LLMs, how many of these demos could you fully recreate if you ignored copyright?

I’ve often reimplemented things at work that exist elsewhere. If I could just copy & paste whole solutions from GitHub and change the branding/naming slightly, I could make curl in an afternoon.

▲

juvoly 4 hours ago | parent | prev | next [-]

So true.

I can only think of hobby projects, like writing yet another emulator, expression parser or media processor in a new language I'm trying to master.

In a professional setting, you would always diligently explore libraries and only implement your own if there is no suitable alternative.

▲

pton_xd 4 hours ago | parent | prev [-]

> how many problems that you work on have many existing free solutions but you neglected to use that code and decided to spend days doing it yourself?

Only when the existing free solutions are licensed with something like GPL. Now I can just say, write me a C webserver library similar to mongoose and I get the functionality without the license burden.

▲

repelsteeltje 4 hours ago | parent | next [-]

You might as well have ignored or removed the GPL notice. Running it through the LLM laundering gets you a "fork" of unknown origin, questionable quality. You're still potentially open to supply chain issues but the chain is obfuscated.

And you now own full responsibility for maintenance.

	▲	grepfru_it 3 hours ago \| parent [-]
		I just vibe coded a socks proxy because existing ones were too thick. And let me tell you, you are absolutely right. Go libraries I’ve never heard of, new implementations that has not been tested.. I think the word for this is YOLO

▲

juvoly 4 hours ago | parent | prev [-]

Indeed, no license burden but you get a maintenance burden instead.

	▲	pton_xd 4 hours ago \| parent [-]
		Well I'd get that either way if I write it myself. Also I was joking, I'd never do that; feels gross. But I suppose it is a legitimate "productive" use of AI.