tag:blogger.com,1999:blog-6628985022531866193.post6647320726872182592..comments2024-02-12T17:37:05.629+00:00Comments on The OldWood Thing: What’s the Price of Confidence?Chris Oldwoodhttp://www.blogger.com/profile/18183909440298909448noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-6628985022531866193.post-9428385869032314832014-10-20T23:45:34.871+01:002014-10-20T23:45:34.871+01:00Hi Chris
You're entirely right that I simplif...Hi Chris<br /><br />You're entirely right that I simplify the implications of releasing more frequently. As with Trunk Based Development and Continuous Integration, Continuous Delivery requires more of an investment in the codebase if it is to be always releasable. Increased complexity due to Feature Toggles, Branch By Abstraction is certainly possible... and choosing where to put the toggle can indeed be tricky if you are writing a high performance system.<br /><br />With Dual Value Streams, the aspiration is for the codebase to always be releasable and to have the same answer for features and fixes i.e. "as quickly as you like". For the majority of organisations that is a long way off.<br /><br />Cheers<br /><br />SteveSteve Smithhttp://www.alwaysagileconsulting.com/blognoreply@blogger.com