Stop sending me huge PRs; a rant

Tired of dealing with massive PRs, a developer expresses frustration about the excessive size of code changes. They argue that small, manageable PRs are easier to write and review, benefiting both the reviewer and the maintainers. The developer believes that the true purpose of small PRs is to provide digestible, reviewable, and understandable sections of work, rather than creating a single, enormous piece of code to be digested all at once.

They suggest that the time needed to fully comprehend a piece of code increases exponentially with the number of lines it contains, causing reviewers to waste an increasing amount of time on larger PRs. The developer questions the need for lengthy comments, stating that proper naming conventions and existing documentation tools (such as jsdoc, rustdoc, and javadoc) are sufficient for understanding code.

For those who advocate using AI to assist in code comprehension, the developer counters that AI tools are already capable, and using them to generate code that requires further human review defeats the purpose. They question the motivation behind submitting large PRs to reviewers, suggesting that it may be a tactic to force approval. In conclusion, the developer urges others to adopt smaller, more manageable PRs to save time and improve code review efficiency.