iambenm
Joined 3 years ago
Joined 3 years ago
Open book tests and allowed cheat sheets already solve the memorization-is-not-required gap. It seems like allowing use of AI pushes that closer to thinking-is-not-required. And if no thinking is required, then how can you prove personal mastery?
Second, if the repo had hooks and instructions for the LLM or user to blindly install/enable the hooks, we'd instead be complaining about security risks and what might happen if the repo is compromised at some point in the future.
Third, sometimes you don't want to mechanically enforce things via git hooks because it impacts your use when what you're really trying to codify and enforce are the LLM's actions. In that case you can enforce mechanically via hooks at the harness level.
And finally, git hooks are a great solution for upstream repositories to enforce quality and protect branches. But it means that the upstream is the one running the checks. It makes the upstream a potential bottleneck - better to have the leaf nodes run the checks locally and fix any issues before pushing it upstream rather than push upstream, wait for results, make changes, push upstream, wait for results, make changes.
[0] https://news.ycombinator.com/newsguidelines.html