logoalt Hacker News

sarchertechtoday at 12:40 AM1 replyview on HN

It’s not about optimizing for performance, it’s about non-deterministic performance between “compiler” runs.

The ideal that spec driven developers are pushing towards is that you’d check in the spec not the code. Anytime you need the code you’d just regenerate it. The problem is different models, different runs of the same model, and slightly different specs will produce radically different code.

It’s one thing when your program is slow, it’s something completely different when your program performance varies wildly between deployments.

This problem isn’t limited to performance, it’s every implicit implementation detail not captured in the spec. And it’s impossible to capture every implementation detail in the spec without the spec being as complex as the code.


Replies

AstroBentoday at 12:59 AM

I made a very similar comment to this just today: https://news.ycombinator.com/item?id=46925036

I agree, and I didn't even fully consider "recompiling" would change important implementation details. Oh god

This seems like an impossible problem to solve? Either we specify every little detail, or AI reads our minds

show 1 reply