DEV Community: Sivasai Nadella

Silent Architect: AI’s Impact on SDLC from PI Planning to Release

Sivasai Nadella — Thu, 25 Dec 2025 17:52:32 +0000

The Silent Architect: AI’s Impact on SDLC from
Artificial Intelligence has moved out of the “experimental lab” stage as a recognized area of expertise. Instead of being a sophisticated autocomplete feature or a script running alone in a void, within a more advanced engineering setting, it finds itself as a majoressler second fiddle who contributes quietly yet significantly across all stages of production plans right up until the finish line.
The best teams aren’t using AI to replace their engineers—they’re using it to alleviate the "cognitive tax" costs associated with modern day software development. Here’s how AI is working its way through the Software Development Life Cycle (SDLC), from grind to craft.

PI Planning: From “Best Guesses” to Data Informed Vision
Planning a Program Increment (PI) can be a marathon for gut decisions. We examine historical velocity, cross our fingers, and hope to plan out the dependencies.
AI is disturbing this balance. AI breathes in the history of sprint data, graphs of dependencies, and incident trends in production. AI serves as reality testers. AI assists teams in:

Predict Realistic Capacity: It marks when a plan is overambitious compared to what has happened in the past.
Expose Hidden "Blockers": It is capable of identifying a dependency between two teams when a human would not see it through all the Jira tickets.
Run What-If Scenarios: Rather than fixed plans that the team could only discuss, AI empowers the lead to run what-if scenarios. “What if we advance that feature? What’s the math likelihood that we won’t meet the release date?”

The End of Vague Requirements
So, who hasn't, at some point, watched a developer step up to a story, only to discover the acceptance criteria (AC) are in disarray? Misguided story descriptions rank high on the list of "wasted sprint cycles."

AI assistants are now helping_Product Owners overcome the gap that exists between business ideas and technical implementation. They can:

Writing "Testable" ACs: Turning "make it fast" into "the page needs to load Largest Contentful Paint (LCP) in 1.2 secs max."
Ambiguity Detection: Ambiguities can be indicated by the AI system even before a single line of code has been written.

Development: AI Agents as Pair Programmers
In the IDE environment, AI tools are manifesting a new evolutionary leap from mere systems of recommendation to context-aware collaborators.
For a large-scale business, it means something beyond just creating boilerplate code. Its sophisticated AI agents can be trained using in-house frameworks. They are also well aware of the architecture and security patterns specific to your business. They assist in:

Onboarding: Explaining legacy spaghetti code to a new hire in seconds.
Consistency: Ensuring that the code developed in Team A is the same as the code developed in Team B.

Testing: Testing Smarter, Not Harder
Traditional test automation is typically “spray and pray,” where everything is run every time. AI brings “Risk-Based Testing.”
Code churn analysis (files with the highest level of changes) normally enables AI to detect high-risk regions and give high-priority treatment to the test suite. AI is also instrumental in detecting flaky tests. These tests are those pesky false positives that reduce the confidence level of the test suite among the development teams.

The Release: Governance Without the Red Tape
The release phase tends to be the most stressing. This is where issues of governance, security, and quality can create a bottleneck. AI eliminates this bottlenecking with functions such as Code Review Agent.

Speed of Thought Security: Rather than running a scan on a weekly cycle, AI understands vulnerabilities as they occur and recommends solutions based on the context of what it knows about the reason it is a vulnerability.
Paperwork Automation: AI can summarize a month’s work into categorized release notes for stakeholders and technical notes for engineers. It takes care of the other checklists for deployment so that people are left to make the "go/no-go" decision.

In "The true value of AI in the SDLC is not automation but augmentation." By thinking of AI as a lifecycle capability instead of a point product, everything changes from being a “threat” into becoming a “teammate.” Instead of trying to eliminate human intuition altogether, it becomes a matter of removing the noise so that human intuition can get on with what really counts – problem-solving and writing great software. The future of engineering will not be about "Human vs. AI." Rather, "Human + AI" will compete with "Complexity."

From Codex CLI to Gemini CLI to Claude Code — AI agents are no longer living inside IDEs; they’ve moved straight into our terminals. These tools can scaffold code, debug entire projects, and even reason across repositories — all through natural language.

Sivasai Nadella — Sat, 25 Oct 2025 21:20:18 +0000

The AI Command Line War: Claude Code vs Gemini CLI vs Codex CLI

Sivasai Nadella ・ Oct 25

#ai #cli #coding #clauda

The AI Command Line War: Claude Code vs Gemini CLI vs Codex CLI

Sivasai Nadella — Sat, 25 Oct 2025 21:16:38 +0000

When the Command Line Became Smart

Remember when the terminal was just a place for running npm install or git push?

Now, it’s becoming an intelligent workspace — a place where you can talk to AI.

Developers today use natural language to scaffold projects, debug errors, or refactor entire repositories. And leading this new movement are Codex CLI (OpenAI), Gemini CLI (Google), and Claude Code (Anthropic).

Each one brings its own personality to the terminal. But which is the right companion for your workflow?

Origins and Design Philosophy

Codex CLI

Born from OpenAI’s Codex model — the foundation for early code copilots — Codex CLI focuses on speed and simplicity. It’s great for quick experiments, scripting, and automation tasks where iteration speed matters.

Gemini CLI

Google’s open-source terminal agent, Gemini CLI, is all about flexibility. It handles coding, research, and shell automation — and can process huge contexts (up to ~1M tokens). It’s a solid choice for large projects and hybrid data workflows.

Claude Code

Anthropic’s Claude Code is the “deep thinker” of the bunch. It’s designed for trustworthy reasoning, excelling at multi-file understanding, code refactoring, and maintaining structural consistency. Perfect for engineers building long-term, production-ready systems.

Feature Comparison

Feature	Codex CLI	Gemini CLI	Claude Code
Context Capacity	Small, fast context for quick tasks	Extremely large (~1M tokens)	Large and reasoning-optimized
Scope	Code generation only	Research + coding + shell actions	Code reasoning & architecture
Output Quality	Fast but basic	Balanced yet verbose	Accurate and deeply contextual
Setup	Simple and lightweight	Requires API tokens	Slightly heavier but robust
Best For	Rapid prototyping	Cross-domain automation	Large-scale codebases

How Teams Actually Use Them

Startups use Codex CLI for fast MVPs.
Data & research teams use Gemini CLI to manage large workflows.
Enterprise teams rely on Claude Code for complex, regulated systems.

Each tool reflects its maker’s DNA:

OpenAI: Speed and usability.
Google: Scale and openness.
Anthropic: Reasoning and safety.

Which One Should You Choose?

That depends on your dev style:

Codex CLI → For rapid iteration and side projects.
Gemini CLI → For big data or multi-modal workflows.
Claude Code → For complex engineering and deep reasoning.

No “best” tool exists — only the one that fits your workflow.

The Bigger Shift: From CLI to Co-Pilot

The real story isn’t just about features — it’s about how we interact with code.

The command line is turning into a conversation layer between humans and machines.

Soon, these tools may evolve into a Cognitive CLI: one that remembers context, learns from your habits, and resolves merge conflicts autonomously.

For now, the best move is simple: experiment. Try them all. See which one feels like an actual teammate.

Final Thoughts

AI-powered CLIs are redefining what “developer productivity” means.

Codex CLI = Agility
Gemini CLI = Range
Claude Code = Depth

The next time you open your terminal, don’t just type commands — collaborate with it.