logoalt Hacker News

semiquaver • today at 6:34 PM • 6 replies • view on HN

Take this as genuine advice, not criticism: The fact that you felt the need to “characterize” the jank and verbally describe it is evidence of your mistake. The only way for these new development models to function is to create a tight machine-only validation loop. Every aspect of an LLM-generated text editor must be drivable fully by the LLM itself so that it can independently observe the problems and fix them (and so those observations can be mechanically translated to regression test cases)

LLMs won’t always guide you to do this correctly so you need to understand how important it is from the start and always enforce it.


Replies

qlte • today at 6:42 PM

I'm not seeing any indication that OP didn't do that. The jank they're describing sounds exactly like something that could slip past the harness' validation loop (weird intermittent graphical anomalies).

jaykru • today at 6:57 PM

I appreciate the friendly tone :-) and I mean this not as a jab: I think maybe you missed the point of my comment above, which wasn't that one can't build functional software with LLMs, but rather that it requires the diligent involvement of a technical worker.

> Barring an architectural paradigm shift we will still need people with strong engineering and design instincts, and even more importantly the ability to write reference code and formal specifications codifying desired behaviors.

The people building those specifications and the tight validation loops you describe are the technical software workers of tomorrow.

➕ show 1 reply
titzer • today at 6:48 PM

Yeah, this is really important. Having a tight test loop is already great for humans, but doubly-so for agents. A clunky manual process sucks for humans and agents alike.

the_real_cher • today at 6:43 PM

I'm not sure you're correct.

If the software was capable of creating high complexity software I, or anyone, should be able to replace and build anything I want with just some prompts and guidance.

Anyone who has worked with LLM heavily knows this is far from the truth.

➕ show 1 reply
groestl • today at 6:42 PM

> always enforce it.

Here be lions, since these things tend to lie to you or themselves when skipping the enforcement part.

asdfman123 • today at 6:47 PM

I find LLMs produce very good results if you just prompt it into good software engineering practices. Write thorough unit tests, minimize diff noise, try to re-evaluate all work to see if it can be done more elegantly and simply. Then you can run an adversarial review agent to catch any bugs it missed.

Same goes for AI slop comments. I can just prompt AI into more or less writing like me.