Writing code and copying the output of an LLM is absolutely not the same.

You wouldn't call someone an author that takes LLM outputs and shoves it in a book. IDK why this distinction doesn't apply to devs too.

▲

peab 2 hours ago | parent [-]

You call someone an author when they use a ghostwriter. They're giving inputs that are core to the output, even though they aren't doing all the writing. Same thing.

▲

shimman an hour ago | parent | next [-]

I can assure you a sizable amount of people in the writing community look down on "authors" that only use ghostwriters.

Why do tech workers act shock that people hate this junk being force fed to them that they are now resorting to violence to reject said junk?

You think telling humans with specialized crafts that they don't matter is good politics? Good grief.

	▲	peab 3 minutes ago \| parent [-]
		Of course. I'm not surprised at all that devs are upset. >You think telling humans with specialized crafts that they don't matter is good politics? Good grief. Yeah, of course not. There are lot's of historical examples of this. That being said, those historical examples don't play out well for the craftsmen, either. Look, I'm a SWE myself. I see my job drastically changing right in front of my eyes. I know there's nuance to it, too, that's hard to articulate in these comment threads. But I think a lot of people here are biased against thinking that they are irreplaceable - I've definitely been in that camp. I don't think that it's wise, however.

▲

QuercusMax 28 minutes ago | parent | prev [-]

Or even more appropriate: a movie director is almost never on-screen but the actors aren't the ones determining the shots to use or writing the script.