Skip To Main Content
Pavan Belagatti on Muck Rack

Pavan Belagatti

India
As seen in: DEV Community, Medium, HackerNoon, YourStory, Linux.com, DZone, Finextra, The New Stack, Jeff Bullas's Blog, Data Science Central, DevOps.com and
AI Evangelist | Developer Advocate | Tech Content Creator
Is this you? As a journalist, you can create a free Muck Rack account to customize your profile, list your contact preferences, and upload a portfolio of your best work. Claim your profile

Get in touch with Pavan

Contact Pavan, search articles and posts on X, monitor coverage, and track replies from one place.

Learn more about Muck Rack

Actions

Share this page

Is this you?

As a journalist, you can create a free Muck Rack account to customize your profile, list your contact preferences, and upload a portfolio of your best work.
Claim your profile

Articles

The Death of the Traditional Software Engineer? Meet the Forward Deployed Engineer (FDE)

|
By Pavan Belagatti
| DEV Community
AI is changing more than the software engineers build. It is changing where they work, how closely they work with customers, and what it takes to get a solution into production. That is why the Forward Deployed Engineer, or FDE, is attracting so much attention. A Forward Deployed Engineer does not simply hand over a product and wait for a customer to configure it.
Open in Who Shared Issue with article?

Context Engineering: The Missing Piece in Agentic Systems

|
By Pavan Belagatti
| DZone Verified
Context engineering is becoming essential as AI agents take on more software development work. An agent can plan, code, test, investigate incidents, trigger CI, and help deploy software. But none of that matters if it is operating without the right information. This is the main problem I keep seeing. We connect an LLM to a few tools, give it a good prompt, and expect magic.
Open in Who Shared Issue with article?

This Is How I Built a Self-Healing CI Pipeline With Agentic AI!

|
By Pavan Belagatti
| DEV Community
TL;DR: A failed CI build is often not just a failed CI build. It is a developer opening logs, scrolling through noise, trying to work out whether the problem came from their code, a flaky test, or a platform issue. A self-healing CI pipeline does not mean an AI system should automatically change production code every time a test fails.
Open in Who Shared Issue with article?
See all 254 articles