Introducing Merged Based Development

Speed up your efficiency and "time-to-merged" by constantly asking what is the minimum viable increment we can merge to the trunk (main branch). The benefits of this approach include faster iterations, fewer bugs, more quality software and happier developers.

Trunk Based Development (TBD) is a popular software development practice that emphasizes continuously integrating code changes into a shared code repository. One of the key benefits of TBD is that it allows developers to collaborate on the same codebase, which can help teams deliver software more quickly. However, to maximize the benefits of TBD, it is important to use small pull requests when merging code changes.

Small pull requests are a natural fit for TBD because they enable faster code reviews. When developers submit small pull requests, it is easier for reviewers to quickly understand the changes and provide feedback or approval. Additionally, smaller pull requests reduce the risk of introducing bugs. When developers make changes in small increments, it is easier to test and validate those changes, reducing the likelihood of introducing conflicts with other changes or other unintended consequences.

Small pull requests also promote better code quality. When developers are working on small and focused changes, they are more likely to write clean, well-structured code that is easier to understand and maintain. This leads to a more maintainable and scalable codebase over time.

In conclusion, Trunk Based Development and small pull requests are two practices that I started to call "Merge Based Development". They help teams deliver software more quickly, with fewer errors, and with better code quality.