Overview
Software development often goes wrong. Very wrong. Trunk-based development (TBD) not only eases the problem, but it helps you make things go very well. In this report, independent technical coach Clare Sudbery explains how TBD has become a technique that many professionals advocate enthusiastically—and one that, for many developers, is essential for continuous integration.
Software development often goes wrong. Very wrong. Trunk-based development (TBD) not only eases the problem, but it helps you make things go very well. In this report, independent technical coach Clare Sudbery explains how TBD has become a technique that many professionals advocate enthusiastically—and one that, for many developers, is essential for continuous integration.
Still, TBD isn't a technique you can adopt lightly. It's very effective for developers who collaborate closely but not very appropriate for open source projects. In order to reap the benefits of TBD, there are several associated practices you need to learn and adopt first. This report helps you get started.
You will:
- Learn about several problems that TBD can handle successfully
- Explore several code integration issues that TBD can help your team manage
- Learn how to write code in tiny chunks, create tests in tandem with code and run them when you commit, and write code designed to be merged several times a day
- Explore the human factor and learn techniques to help avoid the debilitating effects of guilt and shame
- Learn how TBD gets you fast feedback about your code
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Listen now
Unlock full access