- From The Pipeline v36.0
- From the Pipeline v1.0
- From the Pipeline v2.0
- From the Pipeline v3.0
- From The Pipeline v4.0
- From the Pipeline v5.0
- From the Pipeline v6.0
- From the Pipeline v7.0
- From the Pipeline v8.0
- From the Pipeline v9.0
- From the Pipeline v10.0
- From the Pipeline v11.0
- From the Pipeline v12.0
- From the Pipeline v13.0
- From the Pipeline v14.0
- From the Pipeline v15.0
- From the Pipeline v16.0
- From the Pipeline v17.0
- From the Pipeline v18.0
- From the Pipeline v19.0
- From the Pipeline v20.0
- From the Pipeline v21.0
- From the Pipeline v22.0
- From The Pipeline v23.0
- From the Pipeline v24.0
- From the Pipeline v25.0
- From the Pipeline v26.0
- From the Pipeline v27.0
- From The Pipeline v28.0
- From The Pipeline v29.0
- From The Pipeline v30.0
- From The Pipeline v31.0
- From The Pipeline v32.0
- From The Pipeline v33.0
- From The Pipeline v34.0
- From The Pipeline v35.0
The following will be a regular feature where we share articles, podcasts, and webinars of interest from the web.
Final Thoughts on “Patterns for Managing Source Code Branches”
This is the final post in a series on branching from Martin Fowler. The series has been an amazing journey to follow. In the wrap-up, Martin reminds us “branching is easy, merging is harder”. He provides us with a summary of his recommended rules to follow with branching and merging.
If Estimates Were Accurate, We’d Call Them Actuals
A great post from Tanner about establishing a shared understanding on the team about estimates by using metaphors to bring everyone on board. They key point made in this article is: “Estimates are about mathematics. Expectations are about human connection. That difference matters.”
Using Equivalence Partitioning and Boundary Value Analysis in Black Box Testing
A nice introductory article for those in the testing space wanting to learn about equivalence partitioning and boundary value analysis. “Equivalence partitioning and boundary value analysis are two specification-based techniques that are useful in black box testing. This article defines each of these techniques and describes, with examples, how you can use them together to create better test cases. You can save time and reduce the number of test cases required to effectively test inputs, outputs, and values.”
How to Implement Hypothesis Driven Development
Hypothesis Driven Development is about changing the mindset of software development from a set of fixed features to experimentation. Every project becomes an experiment that tests a hypothesis about the system – meaning we can refute the hypothesis and roll back the changes or update our hypothesis and alter our approach.
Five Attributes of a Great DevOps Platform
Pavan Belagatti gives an excellent rundown of DevOps practices an organization needs to adopt to be successful. Some of those practices are building a strong culture of learning, automation wherever possible, and adopting cloud computing.