Everyone preaches 'find vulnerabilities earlier.' The concept is sound. The execution is usually a disaster — every build fails on day one, exception lists grow longer than vulnerability lists, and security becomes a rubber stamp that makes everyone feel safe without actually being safe.
Azure DevOps Pipelines is the CI/CD system enterprise teams end up with because they're an Azure shop. Not because they evaluated the options. Not because they love it. Because it was already there.
The Infrastructure as Code wars are over. Terraform won. And yet enterprise teams are still clinging to vendor-native tooling like ARM templates and CloudFormation because 'it's supported by the vendor.' Supported doesn't mean good.
I've deployed Kubernetes manifests with both Helm and Kustomize across half a dozen enterprise clients. The debate is tiresome. They solve different problems. Here's when each one actually makes sense.
We were using FluxCD to reconcile Kubernetes state from git before anyone called it GitOps. The tooling was raw, the wins were real, and the company that coined the term went bankrupt. Make of that what you will.
Since the 1950s we've been looking for better ways to build software. Iterative development, continuous integration, and SaaS delivery have fundamentally changed the feedback loop — and the winners are those who embrace it.