About
This site is maintained by Jez Humble. The source code for this site is available at GitHub. If you have suggestions on how to improve it, please create an issue. This website is based on Jekyll, and the template is modified from the 18F template. You can find copyright and license information in the footer at the bottom of this page.
If you’re interested in discussing more about continuous delivery, there’s an umoderated continuous delivery mailing list on Google Groups.
Dave Farley is co-author of the original continuous delivery book. He has a blog and a company, Continuous Delivery Ltd, that does consulting based out of the UK.
Biography
Jez Humble is co-author of several books on software: Jolt Award winner Continuous Delivery, Lean Enterprise, The DevOps Handbook, and Shingo Publication Award winner Accelerate. He has spent his career working on code, infrastructure, and product development in companies of varying sizes across three continents, from startups to the US Federal Government, and taught classes in software engineering and product development at UC Berkeley. He was co-founder and CTO of DORA (DevOps Research and Assessment), which was acquired by Google in 2018. He currently serves as a member of technical staff at Anthropic.
Disclosures
I work at Anthropic. This site is not maintained as part of my official work duties, and is not endorsed by my employer. In addition to my compensation, I receive royalties from my books and related content. If you buy my stuff via the links on this site, I get a cut from the vendor, whether Bookshop.org or O’Reilly. All my investments are in wide-ranging mutual funds.
A note on contacting me
The best way to reach me is by email at humble@acm.org, but unfortunately due to the large amount of email I receive I’m afraid I can’t guarantee a response. To increase your chances of a reply try a query that is short and has a simple yes/no answer. In particular, I have learned from experience not to offer advice over the internet. If you’re not sure how to proceed, I have two pieces of general advice: first, work from first principles. Second, apply the scientific method: Mike Rother’s Improvement Kata is an excellent resource.
