Continuous delivery of software often translates into "let's release whatever works without properly architecting the software"
Continuous delivery makes sense if we adopt an experimental mindset. Sometimes that means shipping something half-baked with the intention of testing an assumption or getting feedback, with the expectations of iterating over that.
But as Fabio says in the comment, it should not be an excuse to go fast without accountability
- Continuous delivery works great in complex systems, because The correct response to complexity is probe, sense, respond
