Elektrine lite

← Feed

@alexband@hachyderm.io

Post #3424131

2026-06-26 14:45 UTC

@troed@swecyb.com Suppose you want to contribute a great, much desired feature to one of our open source projects. Some well executed prompts result in a 10K LoC block of code that functionally appears to do what you intended. Before submitting this as a Pull Request to the NLnet Labs team, have you reviewed, do you understand and take responsibility for every line of code that was generated? In our experiences over the last year, this rarely happens. Code is left on our doorstep as a (well intended) gift. But it put the onus on us to review the code, take responsibility for it and merge it into the main branch. Knowing that our software runs in critical infrastructure that power the very fabric of the internet, that is a big ask. As part of our review, we need to be able to have a conversation where both parties understand the ins and outs of the problem space and the solution that is being proposed. That’s not what LLM-use provides the submitter, and it negatively affects the long-term maintenance of the contribution.

Replies (1)

  • @troed@swecyb.com 2026-06-26 14:57

    @alexband@hachyderm.io Nothing in your description has to do with whether the submitter has used an LLM tool or not. You can get slop PRs fully manually typed and great PRs where the contributor has used an LLM. You just described why the policy should deal in quality, not tool usage. (LLMs didn't get good at coding until the last half year or so. Previous experiences are not valid - I didn't consider them useful myself until recently when I challenged my opinions)

    Open ##3424130