The Optimistic Maintainer: Why Fast Merges Beat Endless Review Cycles

Description and use

Optimistic merging in TTT, supported by a robust automated test suite, enabled rapid PR acceptance, sustained contributor engagement, and kept the core binary lean.

Problem

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

Outcome

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.

Workflow

• 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.

Evidence

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.

Source

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.

Source

Merge the 90%.

Source

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

Source

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

Source