|
|
|
|
|
by azdle
703 days ago
|
|
As far as I've seen, LLMs used to write code are only good for getting juniors to a PR features faster. But, it slows down everything else in the process. Reviews take ages because there's random nonsense landmines scattered around, the previous PR feedback is less likely to be applied to later code because they're not writing it, bug fixes take much longer because no one understands the code well, and there's just so much more code to deal with at every step since it doesn't matter to them if they are copy-pasting 10 lines or 1000. I've tried using them myself, but they end up sapping more of my time than they save because of all the dead ends they send me down with plausible sounding bullshit. Things that use real terms, but incorrectly. I basically treat LLM output like that one guy who doesn't know anything except the existence of a bunch of technical terms and who throws those terms around everywhere trying to sound smart. It might be nice to know that a term exists if you're unfamiliar with the topic, but only to go look up what it actually means elsewhere. |
|