Trunk-based development: Increasing engineering velocity and reducing frustration
When working on large projects, there’s a natural tendency to create a branch and start hacking away. When you have a separate branch like this, things tend to balloon. As a developer, you get the urge to refactor all sorts of adjacent things that’ll make your changes cleaner. Before you know it, the scope of your branch is significantly larger than you had originally planned.Even if you stay vigilant about the scope of your branch, you often run into frustrating merge conflicts that can introdu...
Read more at bucket.co