Earlier quoted context omitted.
> I don't know how one can spins this as a bad thing. People spin all kinds of things if they believe (accurately or not) that their livelihood is on the line. The knee-jerk "AI universally bad" movement seems just as absurd to me as the "AGI is already here" one. > Spore is well acclaimed. Minecraft is literally the most sold game ever. Counterpoint: Oblivion, one of the first high-profile games to use procedural te…
> Oblivion, one of the first high-profile games to use procedural terrain/landscape generation I might be misremembering but wasn't the Oblivion proc-gen entirely in the development process, not "live" in the game, which means... > "In the best case, a skilled artist uses automation to fill in mechanical rote work" ...is what Bethesda did, no?
The L in "LLM" Stands for Lying
121–130 of 500 posts
Re: The L in "LLM" Stands for Lying
#122> Video games stand out as one market where consumers have pushed back effectively No, it's simply untrue. Players only object against AI art assets. And only when they're painfully obvious. No one cares about how the code is written. If you actually read the words used in Steam AI survey you'll know Steam has completely caved in for AI-gen code as well. It's specifically worded like this: > content such as artwork,…
> Yeah, exactly. And LLM help developers save time from writing the same thing that has be done by other developers for a thousand times. I don't know how one can spins this as a bad thing Do you ever ask why you're writing the same thing over and over again? That's literally the foundational piece of being an engineer; understanding when you're reinventing the wheel when there's a perfectly good wheel nearby.
f(a, b, c)
It is reusable only if simply changing a, b, c is enough to give the function that you want. Options object etc _parameterise_ that function. It is useful only if the variability in reuse you desire is spanned by the parameters. This is syntactic reuse.With LLMs, the parameterisation goes into semantic space. This makes code more reusable.
A model trained on all of GitHub can reuse all that code regardless of whether they are syntactically reusable or not. This is semantic reuse, which is naturally much broader.
Re: The L in "LLM" Stands for Lying
#123Earlier quoted context omitted.
> I don't know how one can spins this as a bad thing. People spin all kinds of things if they believe (accurately or not) that their livelihood is on the line. The knee-jerk "AI universally bad" movement seems just as absurd to me as the "AGI is already here" one. > Spore is well acclaimed. Minecraft is literally the most sold game ever. Counterpoint: Oblivion, one of the first high-profile games to use procedural te…
> Counterpoint: Oblivion, one of the first high-profile games to use procedural terrain/landscape generation, seemed very soulless to me at the time. Is that even a counter point? Nobody in their right mind would ever claim that procedural generation is impossible to fuck up. The reason Minecraft/etc are good examples is because they prove procedural generation can work, not that it always works.
Re: The L in "LLM" Stands for Lying
#124> Video games stand out as one market where consumers have pushed back effectively No, it's simply untrue. Players only object against AI art assets. And only when they're painfully obvious. No one cares about how the code is written. If you actually read the words used in Steam AI survey you'll know Steam has completely caved in for AI-gen code as well. It's specifically worded like this: > content such as artwork,…
> Yeah, exactly. And LLM help developers save time from writing the same thing that has be done by other developers for a thousand times. Before LLMs we did already have a way to "save developers time from writing the same thing that has been done by other developers for a thousand times", you know? A LLM doing the same thing the 1001st time is not code reuse. Code reuse is code reuse.
Re: The L in "LLM" Stands for Lying
#125I’ve seen reluctance to refactor even 10+-year-old garbage long before LLMs were first made available to the broader public.
Re: The L in "LLM" Stands for Lying
#126Earlier quoted context omitted.
> An LLM has never saved me time. It has always produced something that doesn't quite work, has the rough shape of what I want, but somehow always gets all the details wrong. This reads like a skill issue on your end, in part at least in the prompting side. It does take time to reach a point where you can prompt an LLM sufficiently well to get a correct answer in one shot, developing an intuitive understanding of wha…
I’m curious about how you landed “git gud; prompt better” and not “maybe the domain I work in is a better fit for LLM code”. Or, to be a bit less generous, consider the possibility that the code you’re generating is boilerplate, marshaling, and/or API calls. A facade of perceived complexity over something that’s as complex as a filter-map or two.
It's less "git gud; prompt better", and more, "be able to explain (well) what you want as the output". If someone messages the IT guy and says "hey my computer is broken" - what sort of helpful information can the IT guy offer beyond "turn it on and off again"?
Re: The L in "LLM" Stands for Lying
#127Earlier quoted context omitted.
This geographic protection is extremely bogus in many cases, if not most cases, which imo undermines his argument.
Not really, it's a matter of protecting heritage. Like you can still make Karelian pies[0] anywhere, but unless you follow the exact recipe, you can't sell them as "Karelian pies". It's good for the heritage and good for the customers. You can also make any cheeses and wines and whatever you like, it's just how you name them and market them that's regulated. [0] https://en.wikipedia.org/wiki/Karelian_pasty
Re: The L in "LLM" Stands for Lying
#128What the author and many others find hard to digest is that LLMs are surfacing the reality that most of our work is a small bit of novelty against boiler plate redundant code. Most of what we do is programming is some small novel idea at high level and repeatable boilerplate at low level. A fair question is: why hasn’t the boilerplate been automated as libraries or other abstractions? LLMs are especially good at fuzz…
Because our ways of programming computers are still woefully inadequate and rudimentary. This is why we have a tons of technique for code reuse, yet we keep reinventing the wheel because they shatter in contact with reality. OOP was supposed to save us all in the 1990s, we've seen how it went.
In other fields we've had a lot of time to figure out basic patterns and components that can be endlessly reused. Imagine if car manufacturers had to reinvent the screw, the piston, the gear and lubricants for every new car model.
One example that has bugged me for a decade is: we've been in the Internet era for decades at this point, yet we spend a lot of time reinventing communication. An average programmer can't spend two days without having to deal with JSON serialization, or connectivity, or sending notifications about the state of a process. What about adding authentication and authorization? There is a whole cottage industry to simplify something that should be, by now, almost as basic as multiplying two integers. Isn't that utter madness? It is a miracle we can build complex systems at all when we have to focus on this minutiae that pop up in every single application.
Now we have intelligences that can create code, using the same inadequate language of grunts and groans we use ourselves in our day to day.
Re: The L in "LLM" Stands for Lying
#129A Private (system) Investigator. :)
Re: The L in "LLM" Stands for Lying
#130> Video games stand out as one market where consumers have pushed back effectively No, it's simply untrue. Players only object against AI art assets. And only when they're painfully obvious. No one cares about how the code is written. If you actually read the words used in Steam AI survey you'll know Steam has completely caved in for AI-gen code as well. It's specifically worded like this: > content such as artwork,…
> Yeah, exactly. And LLM help developers save time from writing the same thing that has be done by other developers for a thousand times. Before LLMs we did already have a way to "save developers time from writing the same thing that has been done by other developers for a thousand times", you know? A LLM doing the same thing the 1001st time is not code reuse. Code reuse is code reuse.