I totally get your point but this approach seems a bit dogmatic to me. Even with modern CI/CD techniques and agile methodologies in place, rolling back could st

I totally get your point but this approach seems a bit dogmatic to me. Even with modern CI/CD techniques and agile methodologies in place, rolling back could still be the best choice. For example, always marching forward means that any time an issue is coming up, certain resources must be allocated in tackling the issue. That can't always be the case. Smaller and more frequent releases are preferable and most of the time a single line change will fix the issue, but other times rolling back may be the best option.