4 ms·

Because it produces the desired output. The purpose of a program. There are many domains where an intelligent human can act as a discriminator for output witho

Because it produces the desired output. The purpose of a program. There are many domains where an intelligent human can act as a discriminator for output without knowing exactly in precise detail how the process itself works.

fc417fc802 3mo ago
That is certainly true, but there are also many cases where someone without core expertise who believes themselves to be a capable discriminator actually is not.
- sejje 3mo ago
  Welcome to Earth. I see people parading as experts in all kinds of things all the time, without LLMs to back them up. Political opinions, economic theory, foreign policy, professional sports strategy, who is or isn't intelligent. People blast their very uninformed opinions about these constantly, without realizing they're uninformed. This is a human thing, not an LLM thing. I even have a pet joke about it. Like yesterday I built something in Rust with the LLM -- I'm a total novice in rust. I said "I'm so happy I became an expert in rust today." I built a shed, "so glad I'm an expert carpenter." Some -- maybe most -- people really attach that pin to their lapel with the same amount of experience.
cataphract 3mo ago
Producing the desired output is the purpose of the program, but it's not the only consideration: there's performance, maintainability, security, and so on.
soperj 3mo ago
We had contractors come in to do a project for us once, they had a team of programmers in India as well as a team on the ground. The team in India would produce a bunch of code for them during the night, and they'd review it, and carry on. Things were being done very quickly. Management was happy. Finally after months of this they let us review their code. Turns out that the contractors were just reviewing the output, and they were nailing it. The code itself was absolutely unmaintainable. There was clearly one programmer that had never heard of a jsp, and wrote all of his java to produce html within the java code itself, and another who wrote all of their business logic in scriplets in the jsps themselves. Years later we finally got the okay from management to refactor the whole project. That refactoring project reduced the deployable artifact from over 700mb, to just under 40mb. It reduced a ton of security vulnerabilities and made the code vastly more maintainable, and significantly more performant. The purpose of a program shouldn't be the only consideration unless it's 1 off scripts.

fc417fc802 3mo ago

That is certainly true, but there are also many cases where someone without core expertise who believes themselves to be a capable discriminator actually is not.

sejje 3mo ago
Welcome to Earth. I see people parading as experts in all kinds of things all the time, without LLMs to back them up. Political opinions, economic theory, foreign policy, professional sports strategy, who is or isn't intelligent. People blast their very uninformed opinions about these constantly, without realizing they're uninformed. This is a human thing, not an LLM thing. I even have a pet joke about it. Like yesterday I built something in Rust with the LLM -- I'm a total novice in rust. I said "I'm so happy I became an expert in rust today." I built a shed, "so glad I'm an expert carpenter." Some -- maybe most -- people really attach that pin to their lapel with the same amount of experience.

cataphract 3mo ago

Producing the desired output is the purpose of the program, but it's not the only consideration: there's performance, maintainability, security, and so on.

soperj 3mo ago

We had contractors come in to do a project for us once, they had a team of programmers in India as well as a team on the ground. The team in India would produce a bunch of code for them during the night, and they'd review it, and carry on. Things were being done very quickly. Management was happy. Finally after months of this they let us review their code. Turns out that the contractors were just reviewing the output, and they were nailing it. The code itself was absolutely unmaintainable. There was clearly one programmer that had never heard of a jsp, and wrote all of his java to produce html within the java code itself, and another who wrote all of their business logic in scriplets in the jsps themselves. Years later we finally got the okay from management to refactor the whole project. That refactoring project reduced the deployable artifact from over 700mb, to just under 40mb. It reduced a ton of security vulnerabilities and made the code vastly more maintainable, and significantly more performant. The purpose of a program shouldn't be the only consideration unless it's 1 off scripts.