Chief Roadblock Remover and Learning Enabler | Software Development Expert | Leadership & Career Coach | Speaker | Author | Building great products, building great teams!

🎯 I'm a result-driven 𝗘𝗻𝗴𝗶𝗻𝗲𝗲𝗿𝗶𝗻𝗴 𝗟𝗲𝗮𝗱𝗲𝗿, 𝗦𝗼𝗳𝘁𝘄𝗮𝗿𝗲 𝗗𝗲𝘃𝗲𝗹𝗼𝗽𝗺𝗲𝗻𝘁 𝗘𝘅𝗽𝗲𝗿𝘁, 𝗖𝗼𝗮𝗰𝗵, 𝗧𝗿𝗮𝗶𝗻𝗲𝗿 𝗮𝗻𝗱 𝗖𝗼𝗻𝘀𝘂𝗹𝘁𝗮𝗻𝘁 with more than 20 years of professional experience in different domains, including the 𝗳𝗶𝗻𝗮𝗻𝗰𝗲 𝗶𝗻𝗱𝘂𝘀𝘁𝗿𝘆, 𝗯𝗮𝗻𝗸𝗶𝗻𝗴, 𝗲𝗻𝗲𝗿𝗴𝘆 𝘀𝗲𝗰𝘁𝗼𝗿, 𝘁𝗿𝗮𝗻𝘀𝗽𝗼𝗿𝘁𝗮𝘁𝗶𝗼𝗻, 𝗶𝗻𝘀𝘂𝗿𝗮𝗻𝗰𝗲 𝗮𝗻𝗱 𝘁𝗲𝗹𝗰𝗼. 🚀 My mission is to provide 𝗲𝗻𝗴𝗶𝗻𝗲𝗲𝗿𝗶𝗻𝗴 𝗲𝘅𝗰𝗲𝗹𝗹𝗲𝗻𝗰𝗲 focused on architecture, the best agile practices, passionately 𝗯𝘂𝗶𝗹𝗱 𝗵𝗶𝗴𝗵-𝗽𝗲𝗿𝗳𝗼𝗿𝗺𝗶𝗻𝗴 𝘁𝗲𝗮𝗺𝘀 𝗮𝗻𝗱 𝗼𝗿𝗴𝗮𝗻𝗶𝘇𝗮𝘁𝗶𝗼𝗻𝘀 to deliver innovative, 𝗵𝗶𝗴𝗵-𝗾𝘂𝗮𝗹𝗶𝘁𝘆 𝗽𝗿𝗼𝗱𝘂𝗰𝘁𝘀, working closely with customers and developing software products on different platforms.🎓 As a 𝗿𝗲𝘀𝗲𝗮𝗿𝗰𝗵𝗲𝗿, I published 20+ papers and book chapters in international conferences and journals (having more than 440+ citations and h-index 11 on Google Scholar), obtaining 𝗣𝗵.𝗗. 𝗶𝗻 𝗖𝗼𝗺𝗽𝘂𝘁𝗲𝗿 𝗦𝗰𝗶𝗲𝗻𝗰𝗲𝘀. Also, I have been involved as a 𝗿𝗲𝘃𝗶𝗲𝘄𝗲𝗿 𝗮𝗻𝗱 𝗽𝗿𝗼𝗴𝗿𝗮𝗺 𝗰𝗼𝗺𝗺𝗶𝘁𝘁𝗲𝗲 𝗺𝗲𝗺𝗯𝗲𝗿, member of ACM, the IEEE Computer Society, and GOAI Research group. 🧑‍💼 I work as a professional 𝗛𝗶𝗴𝗵-𝗣𝗲𝗿𝗳𝗼𝗿𝗺𝗮𝗻𝗰𝗲 𝗮𝗻𝗱 𝗖𝗮𝗿𝗲𝗲𝗿 𝗰𝗼𝗮𝗰𝗵 for people in engineering leadership positions.✍🏻 Additionally, I am a 𝗽𝗮𝘀𝘀𝗶𝗼𝗻𝗮𝘁𝗲 𝗮𝘂𝘁𝗵𝗼𝗿, who helps more than 400,000 engineers, managers, and architects to build great careers, products, and teams through various platforms and channels.𝗘𝘅𝗽𝗲𝗿𝘁𝗶𝘀𝗲:📌 Leadership📌 Team building📌 Making things efficient📌 Creating self-contained systems📌 Be highly organized and make others too📌 Focus on strategy/goals📌 Make things happen📌 Career Coaching📌 Mentoring📌 Line management📌 Effective client communication📌 Software Architecture📌 DevOps mindset📌 Cloud (Azure)📌 .NET/C# (ASP.NET/WPF)📌 SQL Server/NoSQL📌 Agile methods (Scrum, Kanban, SAFe)📌 Product/project management📲 Feel free to contact me here via LinkedIn (DM)!

Dr Milan Milanović

Kubernetes killed more startups than server crashes ever did

You don't have Spotify's scale. You have 8 engineers and a single server that's running fine

But you watched a KubeCon talk, and now you've got 23 YAML files, a Helm chart nobody fully understands, and engineers debugging pod evictions instead of buildinga  product

Your "cloud-native infrastructure" is just a cloud bill with extra complexity

A $50/month VM can handle millions of requests. Your startup will run out of money debugging networking issues long before you need horizontal pod autoscaling

The best infrastructure decision is often the simplest one

Chief Roadblock Remover and Learning Enabler | Helping 400K+ engineers and leaders grow through better software, teams & careers | Author | Speaker | Leadership & Career Coach

Friday Developers Fun 🤣

The 5-minute meeting with a developer is not what you think it is

#developers #meme #fridayhumor

𝗔𝗿𝗰𝗵𝗶𝘁𝗲𝗰𝘁𝘂𝗿𝗲 𝗮𝘀 𝗖𝗼𝗱𝗲

We see more tools enabling you to create software architecture and other diagrams as code. 

The main benefit of using this concept is that 𝗺𝗼𝘀𝘁 𝗼𝗳 𝘁𝗵𝗲 𝗱𝗶𝗮𝗴𝗿𝗮𝗺𝘀 𝗮𝘀 𝗰𝗼𝗱𝗲 𝘁𝗼𝗼𝗹𝘀 𝗰𝗮𝗻 𝗯𝗲 𝘀𝗰𝗿𝗶𝗽𝘁𝗲𝗱 𝗮𝗻𝗱 𝗶𝗻𝘁𝗲𝗴𝗿𝗮𝘁𝗲𝗱 𝗶𝗻𝘁𝗼 𝗮 𝗯𝘂𝗶𝗹𝘁 𝗽𝗶𝗽𝗲𝗹𝗶𝗻𝗲 𝘁𝗼 𝗴𝗲𝗻𝗲𝗿𝗮𝘁𝗲 𝗮𝘂𝘁𝗼𝗺𝗮𝘁𝗶𝗰 𝗱𝗼𝗰𝘂𝗺𝗲𝗻𝘁𝗮𝘁𝗶𝗼𝗻.

Another benefit driving the growing use of diagrams-as-code to create software architecture is that it enables text-based tooling, which most software developers already use.

For architecture, as code, we can use different tools, such as:

𝟭. 𝗦𝘁𝗿𝘂𝗰𝘁𝘂𝗿𝗶𝘇𝗿: Create multiple diagrams from a single (C4) model. https://structurizr.com/

𝟮. 𝗣𝗹𝗮𝗻𝘁𝗨𝗠𝗟: It is an open-source tool that allows users to create diagrams from plain text. https://lnkd.in/dWKnyicV

𝟯. 𝗗𝗶𝗮𝗴𝗿𝗮𝗺𝘀: Turn Python code into cloud system architecture diagrams. https://lnkd.in/gPcpcJ7z

𝟰. 𝗠𝗲𝗿𝗺𝗮𝗶𝗱: Generation of diagram and flowchart from a text similar to Markdown. https://lnkd.in/dsTGKbwM

𝟱. 𝗔𝗦𝗖𝗜𝗜 𝗲𝗱𝗶𝘁𝗼𝗿: Free editor for drawing ASCII diagrams. https://asciiflow.com/

𝟲. 𝗠𝗮𝗿𝗸𝗺𝗮𝗽: Could you visualize your Markdown as mind maps? It supports the VS Code plugin. https://markmap.js.org/

𝟳. 𝗚𝗼 𝗱𝗶𝗮𝗴𝗿𝗮𝗺𝘀: Create system diagrams with Go. https://lnkd.in/d-cAq8zB

𝟴. 𝗦𝗲𝗾𝘂𝗲𝗻𝗰𝗲𝗗𝗶𝗮𝗴𝗿𝗮𝗺.𝗼𝗿𝗴: You can create your UML sequence diagrams online using text notation. https://lnkd.in/drux93gN

Image: PlantUML

𝗔𝘇𝘂𝗿𝗲 𝗥𝗼𝗮𝗱𝗺𝗮𝗽 𝗳𝗼𝗿 𝗡𝗘𝗧 𝗗𝗲𝘃𝗲𝗹𝗼𝗽𝗲𝗿𝘀

As a .NET Developer, you probably already know C#, ASP .NET, and other technologies, but in today's cloud-first world, knowing Microsoft Azure is essential for running and deploying your apps. 

This article provides a step-by-step roadmap for .NET developers who want to master Azure, from the basics to advanced DevOps and architecture.

1) Cloud Fundamentals

Lay the foundation so nothing feels mysterious later

• IaaS / PaaS / SaaS distinctions
• Regions & Availability Zones
• SLAs & cost basics

2) Azure Basics

Learn how Azure is organized and controlled

• Azure Portal, CLI & PowerShell
• Microsoft Entra ID & RBAC (access control)
• Resource groups & tags
• Azure Policy fundamentals

3) .NET Compute + Hosting

Deploy your services reliably

• App Service (web app deployment patterns)
• Azure Functions (triggers & bindings)
• Containers fundamentals + Azure Container Registry
• AKS basics (container orchestration)

4) Data Services

Store and connect data with patterns that scale

• Azure SQL + EF Core practices
• Cosmos DB (multi-model, partitioning)
• Blob & Queue Storage essentials
• Service Bus & Event Grid (async/eventing)

5) DevOps & Automation

Shift from manual to repeatable, safe workflows

• GitHub Actions / Azure DevOps pipelines
• Infrastructure as Code: Bicep (Terraform optional)
• Automated builds, tests & gates
• Deployment strategies (canary, blue/green)

6) Security & Identity

Security isn’t optional once you’re live

• Azure Key Vault & secret management
• Managed identities for services
• App security patterns & best practices

7) Observability & Ops

Run it healthily in production, not just launch it

• Application Insights (traces + metrics)
• Log Analytics & KQL basics
• Alerts + dashboards that teams use
• Resilience patterns (retry, circuit breaker)

8) Architecture & Ops

Make systems that tolerate stress and evolve

• Scalability patterns (CQRS, event-driven, partitioning)
• Microservices vs modular monolith thinking
• Cost optimization in design decisions
• Multi-region distribution fundamentals

Cert milestones you can align with:
AZ-900 → AZ-204 → AZ-400 → AZ-305

#dotnet #csharp #azure #cloud #devops

Vibe coding is good at spitting a lot of code, fast

But you still need to know architecture and system design

As well as fundamentals

Because, if you don't, you will get a big ball of mud, fast

𝗬𝗼𝘂𝗿 𝘁𝗲𝗮𝗺 𝗶𝘀 𝘄𝗮𝘀𝘁𝗶𝗻𝗴 𝟰𝟬% 𝗼𝗳 𝗶𝘁𝘀 𝗲𝗳𝗳𝗼𝗿𝘁. 𝗛𝗲𝗿𝗲'𝘀 𝘄𝗵𝗲𝗿𝗲 𝗶𝘁 𝗴𝗼𝗲𝘀

Most engineering leaders blame slow delivery on headcount. The real problem is invisible waste

In 2003, Mary and Tom Poppendieck mapped Lean manufacturing principles to software and identified seven types of waste. Every PR sitting in review, every feature nobody uses, every time a new hire rediscovers what a departed engineer knew, that's waste compounding quietly

But the original seven aren't the whole story. A 2017 empirical study by Sedano et al. observed eight software projects over two years and found new categories

And now there's a new one. GitClear analyzed 211 million lines of code and found that code churn doubled from 2021 to 2024 as AI coding assistants proliferated. Copy-pasted code jumped from 8% to 12%. We're generating waste faster than ever

The good news: once you learn to see waste, you can eliminate it

👉 Full breakdown: https://lnkd.in/d55iaqJu

Greg Coquillo

Product Leader @AWS | Startup Investor | 2X Linkedin Top Voice for AI, Data Science, Tech, and Innovation | Quantum Computing & Web 3.0 | I build software that scales AI/ML Network infrastructure

Product leader with a passion for solving business use cases such as Growth, Go-to-Market, and Price Optimization. I owned P&L for commodity-based products, and leveraged AI to increase the average customer contract values across business industries. As a Product Leader at Amazon, I own a roadmap that drives the adoption of AI products through the Media Automation charter, which supports Private Brands’ YOY growth. I work with Data Scientists, Software Engineers and Business Intelligence Engineers to leverage Machine Learning and Big Data Analytics to design predictive models that enhance business decision-making and performance to accelerate growth, reduce Time to Market of products, monitor cross-geo compliance and import requirements, and ensure customer safety.

I am always curious and eager to learn how new technology affects our daily lives, and I love to support communities on their quest to adopt Artificial Intelligence across industries. Feel free to contact me if you have Data Science projects that you’d like to be showcased on this platform for visibility.

🌐I am a Global Business Leader with 12 years of experience and skills including Product Management, P&L management, Global Networking, EBITDA Optimization, Pricing Management, Margin Management, Product Management, Program Management, Operations and Supply Chain Management, Lean Manufacturing, Six Sigma, and Continuous Improvement.

🧘🏽‍♂️Soft Skills include: Communication, Collaboration, Lateral Thinking, Adaptability, Inspiration, Innovation, Empathy, Listening, Diplomacy, Organization, Responsibility, Leadership...

🎬🎥🎞 I really enjoy watching movies, and if I could redo it all over, I’d be a Sci-Fi script writer so I can be bounded by the limits of imagination.

(Opinions are my own)

Product Management, Media Automation

Owner of the AI vision and roadmap for Private Brand’s Compliance Division. Driving adoption of new technology, allowing my customers to scale their processes and increase productivity. Core responsibilities include:

-Building cross-functional teams consisting of Data Scientists, Software Engineers, Data Engineers, Product Managers and Program Managers, to plan and implement sophisticated AI projects
-Manage the New Initiative Intake Process
-Gather Business requirement artifacts
-Communicate roadmap definition and prioritization
-Coordinate User Acceptance Testing
-Manage Launch Announcements
-Prepare and communicate annual planning artifacts

AI Agents are task-specific, autonomous systems that integrate large language models with structured tools, APIs, and real-time data sources. 

They operate across domains such as cybersecurity, supply chain logistics, and healthcare by executing workflows that traditionally required human-in-the-loop decision making. 

These agents leverage vector databases, retrieval-augmented generation, and fine-tuned embeddings to enable contextual reasoning and dynamic response generation. 

As orchestration frameworks mature, multi-agent systems are increasingly capable of handling end-to-end processes like demand forecasting, patient triage, and adaptive tutoring with minimal supervision.

The below chart shows just how broad their impact is:

1.🔹 IT & Security : Phishing filters, threat detection, patch suggestions
2.🔹Healthcare : Patient alerts, medical chatbots, symptom matching
3.🔹 Education : Flashcards, concept explainers, AI tutors
4.🔹 Sales & Marketing : Lead scoring, campaign ideas, email outreach
5.🔹Logistics : Fleet tracking, demand forecasting, inventory updates
6.🔹Manufacturing : Predictive maintenance, robotic control, energy monitoring
7.🔹 Research : Academic writing, data cleaning, topic expansion
8.🔹 Customer Support : FAQ bots, emotion detection, chat summaries
9.🔹 Smart Environments : Digital twins, voice commands, access control
10.🔹Ops Automation : Shift scheduling, system alerts, order tracking

What used require significant manual effort, now takes a few smart agents.

I believe it’s a great time to start exploring and experimenting in this space…

If you’re learning AI automation without a roadmap, you’re guaranteed to get overwhelmed.

People usually “learn AI automation” by jumping straight into tools… and then wonder why nothing works consistently.
Real automation requires structure - thinking, logic, testing, and a gradual build-up of skills.

This 18-day roadmap breaks down the exact sequence to go from zero → confidently building automations with AI, APIs, tools, and no-code platforms.

Here’s the full breakdown, day by day:

Day 1 - AI Automation Fundamentals
Learn what automation really means, how it differs from AI and agents, and see real examples.

Day 2 - Automation Thinking
Break work into steps, triggers, and outcomes - the mindset behind every good automation.

Day 3 - APIs & Webhooks Basics
Understand how apps communicate and how events trigger workflows.

Day 4 - No-Code Automation Platforms
Explore Zapier, Make, n8n - and how no-code tools actually run workflows.

Day 5 - Build Your First Automation
Create a simple trigger-action workflow and connect two apps.

Day 6 - Data Handling
Pass data between steps, map fields, and work with text, numbers, and dates.

Day 7 - Logic & Error Handling
Add filters, conditional logic, retries, and fallbacks to keep automations reliable.

Day 8 - AI Model Basics
Learn prompts vs system instructions, tokens, limits, and LLM behavior.

Day 9 - Using AI Inside Automations
Insert AI steps into workflows and parse structured AI outputs.

Day 10 - Prompt Design for Automation
Write consistent prompts and reduce hallucinations with JSON outputs.

Day 11 - Text-Based Task Automation
Automate email replies, summaries, CRM updates, and document tasks.

Day 12 - Knowledge Automation (RAG Basics)
Connect AI to internal documents and fetch accurate answers from real data.

Day 13 - AI Agents Basics
Understand agent planning, tools, and identify use cases for agents.

Day 14 - Business Use Case Automation
Automate lead qualification, ticket routing, and internal processes.

Day 15 - Sales & Marketing Automation
Personalize outreach, repurpose content, and automate follow-ups.

Day 16 - Operations Automation
Manage approvals, notifications, and repetitive operational tasks.

Day 17 - Monitoring & Optimization
Track workflow success, cut costs, and improve performance.

Day 18 - Build & Ship Your System
Design, test, document, and finalize a complete end-to-end automation.

You don’t master AI automation by learning tools, you master it by learning systems thinking, data flow, and structured execution.

Follow this roadmap, and you’ll build automations that are reliable, scalable, and business-ready.

Data ➝ AI ➝ Value.
That’s still what companies think AI Looks like

But in the real world…

AI inside companies looks nothing like that.

Because value doesn’t come from “building a model”.

Value comes from building a working system around the model.

This guide explains what AI actually looks like in companies 👇

It’s a full production chain, not a single step:

1) Data
Selection, sourcing, synthesis - getting usable data is already 50% of the work.

2) Data Science
Exploration → cleaning → normalization → feature engineering → scaling
Then modeling: selection → training → evaluation → tuning

3) Value (Operationalizing)
Real value starts only after:
registration → deployment → monitoring → retraining

So ML is not “AI work”.

It’s data engineering + modeling + MLOps, all together.

What GenAI-enabled AI actually looks like

GenAI doesn’t remove complexity.

It shifts complexity from “models” to workflows + control.

The real GenAI path is:

- Understand the decision process
What decisions are being made today? Where does judgment happen?

- Workflow experimentation
Iterate with prompts, APIs, tools, retrieval, automation, coding — until it works reliably.

- Guardrails
Policies, safety filters, access control, cost limits, prompt rules, grounding.

- Monitoring
Track quality, drift, failure modes, user behavior, data leakage, hallucinations.

- Human in the loop
Because the highest-value workflows still need supervision, approvals, and feedback.

The takeaway?

AI isn’t a “feature.”

AI is an operating system change.

And companies that understand this early…

ship faster, safer, and with real ROI.

If you're building enterprise AI, stop chasing “Data → AI → Value”.

Start building: Workflows → Guardrails → Monitoring → Value.

#AI

Knowing RAG is easy. Measuring it is the real skill.

Everyone can plug in a vector DB and call it a RAG system.
But only a few can actually evaluate whether the system retrieves the right knowledge, avoids hallucinations, and answers with confidence.

That’s where retrieval metrics matter, they turn guesswork into engineering.

Here’s a simple breakdown of the 20 metrics that actually show whether your RAG system is good… or just lucky.

1. Precision@K - Checks how many retrieved chunks are truly relevant.
2. Recall@K - Measures whether all important chunks were found.
3. Hit Rate - Confirms if at least one correct chunk appears.
4. MRR - Rewards results where the correct chunk ranks high.
5. NDCG@K - Evaluates ranking quality, not just correctness.
6. Top-1 Accuracy - Tests whether the first chunk is the best one.
7. Query Coverage - Checks if retrieval answers the entire question.
8. Evidence Sufficiency - Asks: “Is this enough to answer fully?”
9. Context Relevance Score - Measures alignment between query meaning and chunk content.
10. Chunk Redundancy Rate - Tracks repeated or duplicate chunks.
11. Chunk Diversity Score - Shows whether results come from varied, reliable sources.
12. Source Coverage - Checks if retrieval pulls from the right documents.
13. Citation Accuracy - Confirms the final answer cites real, correct evidence.
14. Groundedness Score - Tests how strongly the answer stays rooted in retrieved context.
15. Faithfulness - Ensures the model doesn’t distort the evidence.
16. Hallucination Rate - Measures unsupported claims the model invents.
17. Retrieval Latency - How fast chunks reach the model.
18. Token Efficiency - How much useful context fits into the token limit.
19. Freshness - Checks if the retrieved info is up-to-date.
20. Retrieval Failure Rate - Tracks how often retrieval returns irrelevant or misleading chunks.

Anyone can build RAG.
Only skilled teams can measure retrieval, and that’s what decides whether your system scales or breaks.

Which metric do you think is the most underrated right now?

Single agents are powerful.
But multi-agent systems?
That’s where AI starts behaving like a real team.

As AI moves from “answering questions” to doing actual work, the real unlock isn’t a bigger model, it’s how multiple agents collaborate.

Different patterns fit different types of tasks, and choosing the right one can be the difference between a smart system and a chaotic one.

Here are 8 multi-agent collaboration patterns every builder should understand:

1. Manager–Worker Pattern
One agent breaks down the task, others execute the pieces.
Great for large, structured work like research + writing + QA.

2. Specialist Agents (Role-Based Team)
Each agent has a defined role - researcher, analyzer, writer.
Best when accuracy and expertise matter.

3. Planner–Executor Pattern
A planner decides the steps; an executor runs tools and actions.
Ideal for automation tasks, workflows, and system integrations.

4. Critic / Reviewer Agent
One agent generates, another fixes mistakes.
Useful for RAG responses, code checks, compliance-sensitive tasks.

5. Debate Pattern
Agents challenge each other with alternative solutions until the best idea wins.
Good for strategy, architecture, and trade-off decisions.

6. Voting / Consensus Pattern
Multiple agents propose answers, the system picks the best one.
Great for open-ended, ambiguous, or high-risk queries.

7. Swarm / Parallel Exploration
Many agents explore multiple sources at once.
Perfect for fast research and time-sensitive retrieval.

8. Tool Router / Dispatcher Pattern
A router agent decides which tool or agent should handle the request.
Works best in enterprise setups with many databases, APIs, and systems.

AI isn’t becoming powerful because models are getting bigger.
It’s becoming powerful because agents are learning to work together.

This is what turns AI experiments into real products.

Teams get excited about the model… 
but the model is only one slice of the stack.

Real AI products work because every layer around it is engineered with intent.

This breakdown shows what a modern, production-grade AI product stack actually looks like: 

1. Application Layer
The user-facing shell - authentication, UI, APIs, monitoring, analytics. This is where reliability, speed, and trust are felt long before AI runs.

2. Agentic AI Layer
The intelligence engine - reasoning, retrieval, tool use, orchestration, and memory. This layer decides whether your system simply answers… or actually acts.

3. GenAI Ops Layer
The guardrails - tracing, evaluation, experiments, and quality checks. This is how you keep an AI system stable as it learns and evolves in production.

4. Tools & Services Layer
The essentials - model APIs, data warehouses, and external integrations. These services give your AI the inputs, structure, and capabilities it needs to function.

5. Infrastructure Layer
The backbone - compute, storage, GPUs, networking, and security. If this layer is weak, nothing above it scales safely.

AI products don’t succeed because of one great model.
They succeed because every layer, from UI to GPUs - works together as one system.

RAG is not just “upload PDFs + chat with them.”

But that’s like calling every vehicle a “car.”

Because in real AI systems, there are 3 completely different architectures hiding behind the same word:

Naive RAG vs Agentic RAG vs Agentic Memory.

And if you don’t know the difference, you’ll build the wrong system… and blame the LLM later.

Here’s what’s actually happening : 

1. Naive RAG (Basic Retrieval)
Naive RAG is the most common setup: documents get indexed once, stored in a vector database, and whenever a user asks a question, the system fetches the closest chunks and sends them to the LLM. It works well for simple document Q&A, but the accuracy completely depends on retrieval quality  - if the wrong chunk is retrieved, hallucinations become inevitable.

2. Agentic RAG (Tool-based Retrieval + Reasoning)
Agentic RAG is not a fixed pipeline - it’s a decision-making system. Instead of blindly retrieving from a single database, an agent dynamically decides which sources to search, which tools to use, whether the answer needs verification, and when to retry retrieval. This is what enables enterprise-grade search across documents, CRMs, knowledge bases, and even the web - but it also introduces more complexity and cost.

3. Agentic Memory (Long-term Learning Loop)
Agentic Memory is not about pulling knowledge from documents - it’s about building continuity. The system stores useful signals from past interactions (preferences, decisions, repeated tasks, user context) and retrieves them later to give better responses over time. This turns the assistant into something that evolves with usage but if memory isn’t governed properly, it can quickly become noisy, irrelevant, or even risky.

The easiest way to remember it:

Naive RAG = answers from stored docs
Agentic RAG = answers using tools + multiple sources
Agentic Memory = answers that improve over time

If you’re building agents in 2026…
understanding this difference is not optional, it’s architecture.

taplio

The Battle

Dr Milan Milanović

Greg Coquillo

Followers

Posts

Engagements

Likes

Performance ScoreDr Milan Milanović's LinkedIn Performance

Performance ScoreGreg Coquillo's LinkedIn Performance

Ready to grow your LinkedIn presence?

taplio

The Battle

Dr Milan Milanović

Greg Coquillo

Followers

Posts

Engagements

Likes

Performance Score.css-goub6s{font-size:var(--chakra-fontSizes-md);font-weight:500;color:var(--chakra-colors-gray-600);display:block;margin-top:var(--chakra-space-1);}Dr Milan Milanović's LinkedIn Performance

Performance ScoreGreg Coquillo's LinkedIn Performance

Ready to grow your LinkedIn presence?

Performance ScoreDr Milan Milanović's LinkedIn Performance