Comment by pico303

I think you’re missing the underlying point. The Zig team is focused on the contributor and their relationship to the project, not on the correctness of the work. People, not product. Yes, an LLM can help you better understand your code and pick up on things you may have missed before you submit your change. But I think they look at it as you’ve then robbed the Zig team of that interaction with the contributor. They lost the opportunity to learn about how that person thinks, and that person lost the opportunity to be mentored and learn from other members of the Zig team. Sure, your code is better, but did you or the team grow from the experience or simply churn out more code?

I’m not saying whether or not that’s good or bad. I agree with their approach, but that’s just my opinion and who am I to say what’s right or wrong? I think there’s value to LLMs as a tool to search and learn, but I’m also worried that LLMs make it really easy to focus on only the result and not the process. That process can be really valuable in building good teams, while LLMs can be really good at churning out an assembly line of code.