Remix.run Logo
▲ verisimi 2 hours ago

Surely the initial ai responses are a reasonably fair first pass, and would be acceptable to most users.

However, it is then on the person asking the query to refine the query and push for more specifics.

I don't see the problem. Ai doesn't need to get it all right, first time.

▲darepublic 2 hours ago | parent | next [-]

Maybe you aren't trying to solve unique problems? Ie at my job putting together a client side JavaScript async call to db backed endpoint is , for most common cases, solved. It's extremely reliable and can plug in the particulars. But for tasks where it's not rocket science but are unique and not just application of the tired template it's very hard to wrangle it and it's performance varies.It will often.. ignore the particulars and genericize to a more common similar type of problem. Can this be overcome? Sure but it's a tremendous effort almost akin to hand coding everything yourself in the first place.

▲Forgeties79 2 hours ago | parent | prev [-]

> I don't see the problem. Ai doesn't need to get it all right, first time.

Yes it kind of does or it’s not what we were promised/sold. A tool has to work reliably. I don’t want a calculator that’s correct most of the time.

▲foobar10000 2 hours ago | parent | next [-]

So we can add a harness around it? We have decades of experience how to work with faulty sensors, etc… multi-voting, sampling, etc. This will become a part of the harness soon enough . I mean - we can want it to be perfect - sure - but we can deal with imperfect.

▲empath75 an hour ago | parent | prev [-]

> Yes it kind of does or it’s not what we were promised/sold.

No one ever promised this, and in fact, quite the opposite.

> A tool has to work reliably

They work reliably for what they do. You make a request and it returns text. What you _do_ with that text is a question of engineering and process. That are plenty of unreliable steps in business and industrial processes that people _engineer around_. A huge amount of computer chips are just _thrown away_ because of reliability problems in the factories that make them, for example.

> I don’t want a calculator that’s correct most of the time.

An LLM is not a calculator and if you're trying to use it for that, that is a you problem.

▲Forgeties79 38 minutes ago | parent [-]

> An LLM is not a calculator and if you're trying to use it for that, that is a you problem.

I’m talking about another tool. An actual calculator. I would never accept a calculator that is correct “most of the time.” I don’t want an LLM that only meets that bar as well.