September 2023 Summaries

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.

In the world of software development, large tech companies like Google and Meta utilize monorepos to manage their extensive codebases, allowing for unified code across multiple projects and teams. Despite the potential challenges of handling millions of lines of code, techniques like "stacking" enable developers to break down large changes into smaller, more manageable pull requests, facilitating continuous development and minimizing delays. This approach, combined with sophisticated CI/CD systems, ensures seamless integration and delivery of code, mitigating risks of deployment failures. While traditionally the domain of tech giants, tools like Graphite now democratize these practices, enabling smaller teams to adopt stacking workflows and enhance productivity. The evolution of these methodologies highlights how structured processes and advanced tooling can significantly improve code quality and delivery efficiency, benefiting teams of all sizes.

After nearly two years of development and refinement, Graphite is officially launching out of beta, marking a significant milestone for the company. While existing users will see minimal changes, new users can now access the platform without a waitlist, allowing anyone with a GitHub account to engage with features such as creating, reviewing, and merging "stacked changes," a workflow popular at companies like Meta and Google. The move to launch publicly aims to expand Graphite's user base through marketing efforts and capitalize on the need for advanced code review tools beyond what is currently available, primarily on GitHub. This launch signifies Graphite's readiness to scale and challenge the existing market by providing state-of-the-art workflows without altering existing team processes. The development of Graphite has been a journey from a small internal tool to a robust product capable of supporting large-scale engineering collaborations, and the team plans to continue enhancing the platform with features like a desktop app and Graphite AI, while expressing gratitude to their beta community for their invaluable feedback and support.

In the context of a startup, the author reflects on missing the developer tools available at Facebook, particularly the ease of using Interactive Smartlog, a GUI that simplified complex Mercurial commands. The blog post makes a case for the advantages of using a Git GUI, challenging the notion that GUIs are only for beginners and emphasizing their benefits in speeding up workflows, reducing errors, and simplifying complex operations like rebasing. The author argues that GUIs complement command-line proficiency, offering practical advantages for developers of all levels, including experienced ones, by making interactions with version control systems more intuitive and less error-prone. The post highlights various Git GUI tools, such as Graphite Interactive, GitKraken, and Fork, and encourages developers to overcome any stigma associated with using GUIs to optimize their development workflows effectively.

The text explores the extremes of code deployment speeds, comparing the fastest and slowest instances in software development history. It recounts a story of a messaging company that once deployed code changes in as little as 11 seconds by using rsync directly to production servers, demonstrating the potential for rapid deployment. In contrast, it highlights some of the slowest pull requests (PRs) and software projects, such as a PR that took 1,857 days to merge and projects like GNU Hurd and "Duke Nukem Forever" that took decades to see completion, if at all. Despite these historical examples of slow progress, the text notes a modern trend towards faster development cycles, driven by improvements in CI/CD workflows and DevOps practices. It mentions Graphite's role in this acceleration, with features that promise to expedite code review processes and enhance engineering productivity, signifying a shift towards more efficient software development practices.

The Graphite VS Code extension is now available for download, allowing users to visualize and manage their stacks directly within the IDE. It mirrors the functionality of the Graphite CLI by enabling the creation and modification of branches, submission of pull requests, and synchronization of trunk branches, with a particular emphasis on stacking. Additionally, Graphite has introduced a new feature that allows users to commit suggested changes directly from the web app, enhancing collaboration by enabling code suggestions on pull requests. The extension also includes an unresolved comments panel for improved comment visibility, developed in response to user feedback. For Graphite Team or Enterprise users, the Graphite Merge Queue now supports hot-fixing pull requests via label, which can be configured in repository settings.

The official VSCode extension is now available in the Visual Studio marketplace, allowing users to visualize and manage their stacks directly within their IDE. Mirroring the functionality of the Graphite CLI, the extension supports creating and modifying branches, submitting pull requests, and syncing the trunk branch, with robust stacking capabilities. The developers are actively seeking user feedback via their Community Slack server as they iterate on the extension, expressing gratitude to preview users for their early support.