I really enjoy reading this book. After reading some chapters, and parts of the remaining chapters, I think this is one of the important books to read. By important books, I mean;
- Agile Principles, Patterns, and Practices in C# by Robert C. Martin,
- Succeeding with Agile by Mike Cohn,
- Working Effectively with Legacy Code by Michael Feathers,
- Code Complete by Steve McConnell,
- Pragmatic Programmer by Andrew Hunt,
- The Art of Unit Testing by Roy Osherove,
- Facts and Fallacies of Software Engineering by Robert L. Glass
These books are quite practical oriented, and so is Continuous Delivery, but they do not claim it to be an academic book. They answer questions like:
- How long would it take your organization to deploy a change that involves just one single line of code?
- What is a deployment pipeline, and how to avoid antipatterns?
- How do I keep my application releasable?
- Common delivery problems, and how to avoid them?
- Automation over documentation!
- How should I mange a test-system and test-data?
- How do I do zero-downtime releases?
- How do I test non-functional requirements?
This is great! I guess any manager would find this material interesting, as it saves a lot of time and increases quality by a light-year.
As a developer I find it interesting because they bridge a gap between the IT-guys and the developers. Continuous Delivery is a step further from continuous integration. CI is a part of the CD process.
Read it, and you will be inspired! Do it, and you will succeed!
