The Optimistic Maintainer: Why Fast Merges Beat Endless Review Cycles

说明与用途

TTT 项目通过“乐观合并”策略和完善的自动化测试体系，实现了快速合并 PR、保持核心二进制体积小巧，并提升了贡献者参与度。

问题

Maintainers often create friction by over‑reviewing PRs, causing contributor burnout and slow release cycles.

结果

Optimistic merging, backed by a robust automated safety net, enabled TTT to merge PRs within hours, keep the core binary lean, and grow a vibrant contributor community.

工作流

• 1. Ensure a comprehensive automated test suite (3,500+ tests, deterministic UI snapshots, benchmark comparisons, architectural zones).
• 2. Apply the 90% rule: merge PRs that pass CI and cover 90% of the problem, then handle remaining 10% via follow‑up tickets or quick polish commits.
• 3. Defend scope: accept bug fixes and quality code but redirect feature requests that fall outside core into Lua plugins.
• 4. Encode culture in code by generating a contributors.json script that lists code authors and issue reporters, embedding it in the binary for acknowledgment.

证据

If merging a PR requires you to open the editor and manually poke at things to see if it feels right, you will inevitably become a bottleneck.

来源

Because the machine ruthlessly verifies that the invariants haven't broken, I don't have to spend my mental energy acting like a human compiler.

来源

Merge the 90%.

来源

By pushing niche features into plugins, the core binary stays lean (single static Go binary, ~14 MB).

来源

Every bug reporter and every code author is literally baked into the application they helped build.

来源