Hacker News Reader

Crazy how this doesn't register in people's heads. Has the real bottleneck ever been code written and not the review of code and everything involved? Understanding the nuance and implications behind design decisions; strategy.

In any REAL, workload, with good processes, code review makes speed of code generated a moot point. You still move as fast as you can review the code, and no, I won't debate that you can rely on LLMs, a deterministic language predictor, to determine the correctness of code; in the context of the business, and technical implications.

That is indeed the point I was making.

Where is the real bottleneck, if I may ask?

> verifying the correctness of LLM-generated code

It's... pretty clear in the original conversation.

I find that people who write "may I ask" are often/usually bad-faith arguers under cover of being polite.

That's a good rule of thumb, it seems that way more often than not.

If you are a responsible maintainer you need to verify the correctness of the contribution wether you used an LLM to generate it or wether someone else did.

Having someone else be the AI-middlemen, just introduces additional complexity and confusion.