Code Ownership: Using CODEOWNERS Strategically
Code ownership boosts accountability and speeds up reviews. Use CODEOWNERS strategically to align teams, reduce delays, and keep your codebase healthy.
Code Ownership: Using CODEOWNERS Strategically
Code ownership boosts accountability and speeds up reviews. Use CODEOWNERS strategically to align teams, reduce delays, and keep your codebase healthy.
Shantanu Das
Read the articles by Shantanu Das in the Aviator blog. Get professional advice on software product deployment, testing, and other engineering topics.
Code Reviews at Scale in Monorepos: Using CODEOWNERS and GitHub Actions for Automation
As teams scale and repositories grow, especially in monorepos, code reviews can become a bottleneck rather than a safeguard.
LLM Agents for Code Migration: A Real-World Case Study
LLM agents are changing how developers handle code migration turning tedious, error-prone refactors into intelligent, semi-automated workflows. In this case study, we show how agents migrated a Java codebase to TypeScript by analyzing code, planning steps, and executing changes with architectural awareness and CI-backed validation.
Java Version Upgrade: A Hands-on Guide from Java 8 to 17
Learn why upgrading from Java 8 to 17 matters in 2025, and how to do it right with new features, better performance, and modern tool support.
Technical Debt and the Role of Refactoring
Fast software delivery often builds up technical debt. Learn how continuous refactoring helps manage debt, improve code quality, and support growth.
Top 8 KPIs for Release Management
Release management ensures smooth software deployments with minimal disruptions. Tracking key KPIs like Deployment Frequency, Change Failure Rate (CFR), and MTTR helps teams improve efficiency, reduce downtime, and enhance stability. In this blog, we break down the top 8 KPIs that drive successful releases.
Monorepo vs Polyrepo: Which Repository Strategy is Right for Your Team?
Shifting from a monorepo to a polyrepo isn't just a matter of splitting code it's a rewrite of your entire developer workflow. Dependency boundaries, shared libraries, and tightly coupled CI/CD pipelines often make the transition painful. In this post, we explore when each model works best, why companies like Facebook and Netflix took different paths, and what to consider before making the switch.
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.
Top 10 Developer Tooling for 2025
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…
How to Git Undo Commit: Methods and Best Practices
Made a mistake in Git? No worries! This guide covers git reset, git revert, and git reflog to undo commits safely, whether they’re local or already pushed. Learn when to keep, unstage, or discard changes and how to recover lost commits.
Why Trunk-Based Development Is Key to Successful Continuous Delivery
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
