Comment by sarchertech
12 hours ago
This:
> In the pre-LLM era, the economic value of "understanding" and "shared knowledge" about the programs themselves was only that it made maintenance and changes cheaper.
This only holds if there is a bright line separation between the problem, the solution, and the implementation of the solution. And that is not the case.
Understanding the implementation frequently improves your understanding of the solution, which improves your understanding of the problem, which leads to better solutions. Sometimes it leads to realizing that there is a completely different problem you should be solving.
So what I’m refuting is that there is no value to understanding the program.
But beyond that black box products that users know how to use but don’t understand is also a vast oversimplification.
Frequently software is useful specifically because it forces users to adopt a process not just because it allows them to do something they were previously doing faster. In those cases the process is usually informed by the implementation, so the user needs to understand parts of the implementation even if it’s indirectly.
Yes, you're right, understanding informs the constraints and the possible solution spaces. That should be added to the list.
Practically speaking, I don't think the "black box" metaphor is as broken as you're saying, though I like the point you made. There is still a ton of software (the majority, I think -- crud apps of all flavors) where an unthinking, untechnical PM wants something they can specify, and an LLM can give it to them, and it will more or less solve their problem. It won't be the best possible thing, but it will be good enough.