The thing is that a "very high standard" is not a measurable criterion. The project can have test coverage requirements and strict linting to catch basic syntax and logic problems, but how do you enforce simplicity, correctness, robustness, or ergonomics? These are abstract concepts that are difficult to determine, even for experienced developers, so I wouldn't expect less experienced developers to consider them. A code review process is still important, with or without LLMs.
So we can ask everyone using these tools to understand the code before submitting a PR, but that's the best we can do. There's no need to call anyone out for not meeting some invisible standard of quality.
Re:Writing Code Was Never the Bottleneck
by aleph_minus_one on Thursday July 03, 2025 @03:51PM
(#44458597)
The answer is simple: "a very high standard" is what the very experienced developers of the team consider to be "a very high standard". :-)
Re:Writing Code Was Never the Bottleneck
by mrguyorama on Thursday July 03, 2025 @06:03PM
(#44459544)
The developers who try to hold a "very high standard" will be accused of blocking progress and fired.
Re:Writing Code Was Never the Bottleneck
by aleph_minus_one on Thursday July 03, 2025 @06:57PM
(#44459807)
Under a bad management, this might indeed (unfortunately) happen. :-(
It is likely not possible to completely forbid junior developers from using AI tools, but any pull request that they create that contains (AI-generated) code that they don't fully comprehend (they can google) will be rejected (to test this, simply ask them some non-trivial questions about the code). If they do so, again, these junior developers deserve a (small) tantrum.