He is a Principal Consultant at ThoughtWorks, where he has been for over seven years. He has worked with a variety of companies in multiple domains, and currently runs the Cloud & Continuous Delivery Practices for Europe. He has written articles of O'Reilly, presented at conferences, and sporadically commits to open source projects. Principally a Java developer, he also spends lots of time with Clojure and Python, and build systems that hate him.
This talk focuses on the kinds of constraints we should consider when evolving their architecture of our systems in order to enable rapid, frequent release. So much of the conversation about Continuous Delivery focuses on the design of build pipelines, or the nuts and bolts of CI and infrastructure automation. But often the biggest constraint in being able to incrementally roll out new features are the problems in the design of the system itself. I'll be pulling together a series of patterns that will help you identify what to look for in your own systems when moving towards Continuous Delivery.