Dec 3, 2024
"As we can only rotate on code that can be integrated into Trunk, we are incentivized to take small steps. The smaller the step, the faster we can rotate. The more we rotate, the more engagement we feel as a group."
seen from China
seen from United States
seen from United States
seen from United Kingdom
seen from United States
seen from United States
seen from Germany
seen from United Kingdom
seen from Australia
seen from United States
seen from United States
seen from United States
seen from United Kingdom
seen from Maldives
seen from Italy
seen from Singapore
seen from Italy
seen from Malaysia
seen from Hong Kong SAR China
seen from United States
"As we can only rotate on code that can be integrated into Trunk, we are incentivized to take small steps. The smaller the step, the faster we can rotate. The more we rotate, the more engagement we feel as a group."
Trunk-based development When it comes to software delivery speed and quality, trunk-based development is the way to go. It took me a while to realize this myself. I used feature branches with pull-request as the main way of working (writeup of an experience of using pull request), so well aware of the advantages and disadvantages. But switching to Trunk based development felt very counterintuitive to me. For sure the build would be broken all the time and the quality would be horrible, especially with a larger group of people?
Great resources by Nelis Boucke on how to get started with #trunkbaseddevelopment.
“If you want real-world public examples of trunk-based development? Check out the replies to this tweet. https://t.co/hfCnhn9gsC”