O'Reilly logo
  • Erdem Azaklı thinks this is interesting:

With the automation of the release process complete (and repeatable and reliable) we, as developers and operators, have confidence in continually releasing new functionality without causing breakages or regressions. Nothing destroys morale as quickly as have to rely on an unreliable and flakey deployment process. This leads to fear in deploying code, which in turn encourages teams to batch large amounts of functionality in “big bang” release, which ultimately leads to even more problematic releases. This viscous feedback loop must be broken, and the adoption of the continuous delivery of functionality in small batch sizes (ideally with single piece flow) is a great approach to help encourage this.


Cover of Continuous Delivery in Java