Shantanu Das

Shan is a contributor at Aviator’s blog, where they cover developer experience tooling, CI/CD workflows, and engineering productivity trends. With a knack for breaking down complex tech topics into clear, actionable insights, Shan helps teams streamline developer workflows and ship high-quality software faster.

Automated Failover and Git Rollback Strategies with GitOps and Argo Rollouts

When Kubernetes deployments fail due to misconfigurations, manual rollbacks are slow and disruptive. GitOps, with ArgoCD and Argo Rollouts, automates failover by detecting issues and reverting to the last stable version. ArgoCD enforces Git as the source of truth, while Argo Rollouts manages progressive deployments, preventing faulty updates from reaching users and ensuring rapid recovery.
Shan is a contributor at Aviator’s blog, where they cover developer experience tooling, CI/CD workflows, and engineering productivity trends. With a knack for breaking down complex tech topics into clear, actionable insights, Shan helps teams streamline developer workflows and ship high-quality software faster.
Avatar photo

Shantanu Das

Shan is a contributor at Aviator’s blog, where they cover developer experience tooling, CI/CD workflows, and engineering productivity trends. With a knack for breaking down complex tech topics into clear, actionable insights, Shan helps teams streamline developer workflows and ship high-quality software faster.

Automated Failover and Git Rollback Strategies with GitOps and Argo Rollouts

git rollback strategies

When Kubernetes deployments fail due to misconfigurations, manual rollbacks are slow and disruptive. GitOps, with ArgoCD and Argo Rollouts, automates failover by detecting issues and reverting to the last stable version. ArgoCD enforces Git as the source of truth, while Argo Rollouts manages progressive deployments, preventing faulty updates from reaching users and ensuring rapid recovery.

Top 10 Developer Tooling for 2025

top 10 developer tooling

Developer Experience (DX) is about making it easier for developers to build, test, and deploy applications. A good DX reduces setup complexity, speeds up workflows, and minimizes technical hurdles, allowing developers to focus on writing clean code and solving real…

Why Trunk-Based Development Is Key to Successful Continuous Delivery

continuous delivery with trunk based development

Trunk-based development enables faster, more reliable software deployment by making frequent, small commits to the main branch. This approach minimizes integration issues, supports continuous delivery, and enhances stability through automation, feature flags, and short-lived branches. This blog explores how trunk-based development aligns with CI/CD pipelines and offers best practices and tools to optimize workflows and maintain build stability.

Impact of Flaky Tests in Merge Queue

Flaky tests, which fail unpredictably without changes in code or environment, can cause significant delays in development. They disrupt merge queues by blocking valid pull requests, leading to resets, wasted resources, and frustration among developers. Merge queues are designed to streamline the integration process, but flaky tests undermine their efficiency. Tools like Aviator MergeQueue help manage these challenges with features such as parallel testing and early validation. By addressing flaky tests and stabilizing testing environments, teams can ensure smoother workflows and more reliable CI/CD pipelines.

Subscribe

Be the first to know once we publish a new blog post

Join our Discord

Learn best practices from modern engineering teams

Get a free 30-min consultation with the Aviator team to improve developer experience across your organization.

Powered by WordPress