Great post. I could not agree more. To further the article, CI/CD are often neglected by small teams / startups. However, startups would benefit more than large teams (as a percent of time) by automating the build and deploy processes.<p>The only point I've heard a counter to is "Automate Rollback". Noah Sussman (previously of Etsy) mentioned that they never rolled back (at a Groupinar). When a bug was pushed to production, they would fix in dev, test, and deploy. If I remember correctly, he mentioned their time to fix was < 7 mins (or better).<p>Also, when I first started in my career, one of our most senior admins stated something very similar. In a meeting, I suggested we have a rollback mechanism. The response was that code is like a river, keep it moving in one direction.<p>In practice, I've found that rollbacks should be reserved for catastrophic events where you are literally running your deployment software to reset infrastructure, dependencies and application code.