3 ms·
I disagree with some of the conclusions. CD is avoided because most software products should not be delivered continuously, as it is inversely correlated to so
by hctaw 6y ago
I disagree with some of the conclusions.
CD is avoided because most software products should not be delivered continuously, as it is inversely correlated to software stability for customers. It may create value internally, but if it doesn't create value externally and is cheap to roll out then it's probably not worth it.
Slightly related, I think CI/CD is today where VCS was before git. It all kinda sucks, and no startup or company is going to fix it (nor can they, it must be free as in beer and speech). We need something that sucks less and becomes as standard a tool as git or make.
- choeger 6y agoGood point. Imagine the developers of Postgres or Mongo would do CD to your database. IMO, the idea of CD only works for companies that control the production environment and basically offer a service, not a product. If that's you, you may get a great deal out of CD. But if you have a product and if that product manages your customer's data, is integrated with your customer's scripts, and runs on an environment that you don't completely control, you better think twice before permanently updating the system. You can still do it, but it will be expensive to get it right.
- lgunsch 6y ago> CD is avoided because most software products should not be delivered continuously, as it is inversely correlated to software stability for customers. This has been shown to be flat out wrong. Stability has been shown to be highly correlated to the capacity to deploy quickly and often. https://www.goodreads.com/book/show/35747076-accelerate https://www.goodreads.com/book/show/35747076-accelerate https://nicolefv.com/research https://nicolefv.com/research