3 ms·
maybe you are not bottlnecked by coding. but there is high probability that you will be bottlenecked by verifying the correctness of LLM-generated code.
by chenzhekl 5mo ago
maybe you are not bottlnecked by coding. but there is high probability that you will be bottlenecked by verifying the correctness of LLM-generated code.
- grokys 5mo agoThat is indeed the point I was making.
- amelius 5mo agoWhere is the real bottleneck, if I may ask?
- solid_fuel 5mo ago> verifying the correctness of LLM-generated code It's... pretty clear in the original conversation.
- saulpw 5mo agoI find that people who write "may I ask" are often/usually bad-faith arguers under cover of being polite.
- solid_fuel 5mo agoThat's a good rule of thumb, it seems that way more often than not.
- notnullorvoid 5mo agoIf 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.
- Bridged7756 5mo agoCrazy 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.