Author here. Pointing out that we can't hold entire projects in our heads is not a made up excuse. And doing things like breaking things up into modular components that have specifications and tests is precisely how we combat cognitive complexity. That's exactly the approach I am taking with Jolt where there is a large specification and conformance harness used to ensure semantic correctness of the language. https://github.com/jolt-lang/jolt/tree/main/test/conformance
Meanwhile, anybody who's maintained a large scale software project knows that even with the best practices, problems can still be introduced into the codebase. Nobody is arguing against limiting context or doing as much as possible to ensure the contribution is doing the right thing. Yet, the idea that you can have full understanding of how the feature will interact with every edge case is frankly laughable.
The notion that you can architect a perfect codebase where context and scope of the effect of any change is always completely clear is idealistic in the extreme. Of course, we should strive to keep the code quality as high as possible, nobody is arguing against that. The reality is that large projects are complex, and nobody has come up with a way to write code in the way where it's possible to perfectly control the scope of the effects of any one change. Every single large scale project out there has bugs, and regressions no matter how much the authors strive to make it perfect.
> I get the impression that you must be new in your programming career, and hold idealistic views of the reality of what maintaining large projects looks like in practice.
Personal attacks for someone pointing out some issues with the LLM apologetics. Nice.
disclaimer: 27 year professional in this field and I mostly agree with OP.
> Yet, the idea that you can have full understanding of how the feature will interact with every edge case is frankly laughable.
That's not what I'm saying. What I'm saying is that the contributor should make a reasonable attempt at producing a bug free patch. And it's up to the project's leaders to make it easy to do so. And one of the easiest way for the latter to do so is producing design docs and isolating modules as much as possible so that it's efficient to get the needed understanding.
So both parties each have its own responsibilities into making quality contributions happen. I'm not against LLM usage. What I'm against is making the project difficult for human understanding because human understanding is limited or whatever. That's why I point out the README and the Makefile.