The discussion surrounding the optimal way to communicate code changes has persisted since the era of punch card programming, with differing opinions on how best to write pull request (PR) titles and commit messages. While organizations and open-source projects often set their own guidelines, the article explores a data-driven approach to optimizing PR titles for faster review times. An analysis of two million PRs suggests that titles should be short (under 40 characters), use lowercase, contain exclamation points, avoid curse words, and prefer the word "fix" over "feat" to maximize review speed. These strategies could significantly reduce the waiting time for reviews, saving engineers considerable time annually. The piece emphasizes that although engineers aren't entirely stalled during review waits, optimizing PR titles could enhance efficiency, with Graphite offering tools to support this practice.