Was initially interested (I like languages that binds easily to C because of the nice libraries there, and I'm a fan of LISP), but the README is LLM-generated and the Makefile is unreadable. The there's this part in the AI policy<p><pre><code> It is simply not feasible for humans to keep the entirety of large projects in their heads all at once. When working on a project, one is constantly forgetting and relearning code along the way. The situation is even worse for projects where multiple people work together and no one knows what everyone else was thinking. We look at the code and try to build up sufficient context in our heads to make the necessary changes. When we misjudge that context or misunderstand existing code, we end up making mistakes.
</code></pre>
It's a made up excuse because no one has ever tried doing that. Instead the core activity of software engineering (and engineering in general) is to break down things into modular components, ensure that they work well, produce specs, then assemble the result. Which is why no one read the source code for open(2) system call before using it. Instead they read the manpage and only when there's an issue there's a need to compare the specs with the implementation.<p>So it's a matter of communication between humans. If person A is responsible for module 1 and person B's module 2 depends on the former. It's up to A to provide a proper spec to B. It's not up to B to learn everything about module 1's implementation and doing so is kinda foolish.<p>So something like<p><pre><code> Any new code that is added is therefore always done with limited understanding.
</code></pre>
Is a red flag. The codebase and workflow should be that new additions should deal with a limited context (as in one PR shouldn't touch unrelated things) at at time and the contributors should be able to come with a full understanding of what they are doing. If they cannot, it's either a failure of the codebase, the docs, the workflows, or the contributors.
I’m not even sure I agree it’s impossible for one person to understand a large codebase. It’ll depend on size of course but plenty of major pieces of software have been developed by a single person capable of understanding the whole codebase.
I've developed plenty of large software projects, and what happens in practice is that you build up the context for the part of the project you're working on when you make changes. If you could just hold the entirety of the project in your head we wouldn't need tools like debuggers or test harnesses at all. You'd just know that all the changes you made are correct. That's obviously not how things work in the real world.
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. <a href="https://github.com/jolt-lang/jolt/tree/main/test/conformance" rel="nofollow">https://github.com/jolt-lang/jolt/tree/main/test/conformance</a><p>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.<p>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.
> Yet, the idea that you can have full understanding of how the feature will interact with every edge case is frankly laughable.<p>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.<p>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.
> 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.<p>Personal attacks for someone pointing out some issues with the LLM apologetics. Nice.<p>disclaimer: 27 year professional in this field and I mostly agree with OP.
Anyone who's seen the author communicate here and on Lobsters will know that this particular critique irks them and they tend to react exactly like this when it comes up. It's a sore spot, and one the author should probably try to work through on their own since they seem to spend a lot of time vibecoding things.
If you have 27 years of professional experience in this field and still think that you can have total knowledge of how a piece of functionality interacts with the overall codebase in a large software project, then I really don't know what to tell you. If that was the case we'd be writing perfect software that never has bugs.<p>Also, I have no idea what any of this has to do with LLMs. Nothing discussed here was LLM related in any way. Nor am I doing any apologetics for anything here. I'm stating basic facts that anybody with even a modicum of intellectual integrity would acknowledge.<p>But if you have any actual counterpoints to what I said then feel free to share them.