The slides used for this session are available to download from here.
Branching during the evolution of a software product, either its over-use or complete avoidance, is just as susceptible to the malaise of the 'cargo cult' as many other areas of development. The choice is not always made based on an informed decision with a careful weighing up of the pros and cons and their alternatives, but purely by following what practices the 'cool' companies are (seen to be) using.
What is often misunderstood is how the same risks that historically have been mitigated through the use of branches might now be handled via the use of other, non-version-control related practices to ensure stability and productivity remains high in the face of continued change. Whilst there is still a time and a place for the use of branches, we will discover when that might be, but equally spend as much time exploring the complimentary practices that help us to avoid their pitfalls.
Chris is a freelance developer who started out as a bedroom coder in the 80’s writing assembler on 8-bit micros; these days it’s C++ and C# in plush corporate offices. He also commentates on the Godmanchester duck race and can be contacted via firstname.lastname@example.org or @chrisoldwood.
To ensure you're the first to hear about Agile Cambridge 2017, join our mailing list.