The rise of async AI programming

(www.braintrust.dev)

123 points mooreds | 2 comments | 11 Sep 25 12:20 UTC | HN request time: 0.501s | source

Show context

jmull ◴[11 Sep 25 15:47 UTC] No.45212981[source]▶

This vision of AI programming is DOA.

The first step is "define the problem clearly".

This would be incredibly useful for software development, period. A 10x factor, all by itself. Yet it happens infrequently, or, at best, in significantly limited ways.

The main problem, I think, is that it assumes you already know what you want at the start, and, implicitly, that what you want actually makes some real sense.

I guess maybe the context is cranking out REST endpoints or some other constrained detail of a larger thing. Then, sure.

replies(4): >>45213325 #>>45213917 #>>45214051 #>>45215057 #

1. thefourthchime ◴[11 Sep 25 16:15 UTC] No.45213325[source]▶

>>45212981 #

I disagree with being detailed, many times I want to AI to think of things, half the time it comes up with something I wouldn't have that I like.

The thing I would add is to retry to prompt, don't tell it to fix a mistake. Rewind and change the prompt to tell It not to do that it did.

replies(1): >>45214155 #

2. athrowaway3z ◴[11 Sep 25 17:42 UTC] No.45214155[source]▶

>>45213325 (TP) #

I agree there is a lot of value to have it do, what it considers, the obvious thing.

It is almost by definition what the average programmer would expect to find, so it's valuable as such.

But the moment you want to do something original, you need to keep high-level high-quality documentation somewhere.

↑