3 ms·

I disagree. I believe that a critical part of software engineering is the ability to trace and resolve an issue through many different systems and code paths (

I disagree. I believe that a critical part of software engineering is the ability to trace and resolve an issue through many different systems and code paths (what most people call debugging) There is no way to debug these models, there is no way to systematically fix your prompts. It is therefore completely guesswork on what words in what orders might produce results closer to what your stakeholders expect. Software engineers, when presented with an issue, can dive down as deep as they want (hell, even to the machine code layer if it comes down to it) in order to fine-tune, fix bugs, or do whatever else a stakeholder might expect. Two very different coins in two very different universes.

capableweb 4y ago
> There is no way to debug these models, there is no way to systematically fix your prompts. It is therefore completely guesswork on what words in what orders might produce results closer to what your stakeholders expect. I think if you spend some more time with these models, or any similar model where you have X input > Y output, you notice that you can in fact "debug" those as well, without knowing 100% of the internals. Some fixes are better than others. There are better and more reliable ways to steer these models, compared to other ways. It is not 100% guesswork, some people are better at it than others.
- lupire 4y ago
  But you can't get too far. It's like trying to design a pharmaceutical without using a microscope or chemistry to study the target system, just throwing drugs at a human model and seeing what happens.