#Communication

Communication patterns define how agents exchange information and coordinate actions. Posts cover A2A protocol-based inter-agent communication, Microsoft Agent Framework message routing, and the architectural patterns that enable agents to collaborate without tight coupling.

9 posts tagged with communication. ← All posts

#A2A (14)#ADK (8)#AG-UI (6)#AI (9)#AI Agents (311)#AI Architecture (10)#AI Cost (10)#AI Cost Optimization (8)#AI Engineering (201)#AI Evaluation (8)#AI Governance (29)#AI Red Teaming (9)#AI Research (9)#AI Safety (8)#AI Security (21)#AI in Production (12)#AML (3)#API Design (10)#API Security (8)#APIs (55)#AWS (17)#Accounting (9)#Agent Skills (3)#Agentic AI (24)#Agentic Commerce (12)#Agentic RAG (8)#Agents (4)#Amazon Bedrock (8)#Analytics (3)#Architecture (36)#Audit (3)#Authentication (11)#Authorization (3)#Automation (6)#Azure (11)#Azure AI Foundry (9)#Backend Engineering (310)#Benchmarks (3)#Best Practices (3)#BigQuery (6)#Business Finance (8)#Business Strategy (55)#C (8)#CI/CD (8)#Caching (10)#Capital Markets (14)#Card Payments (12)#Cards (13)#Career (24)#Checkpointing (4)#Claude Code (8)#Cloud (5)#Cloud Architecture (3)#Cloud Native (10)#Code Review (8)#Collaboration (5)#Communication (9)#Compliance (52)#Computer Networking (9)#Computer Science (32)#Computer Vision (5)#Concurrency (37)#Consulting (3)#Containers (10)#Context Engineering (10)#Cost Optimisation (5)#Credit (14)#Credit Risk (14)#CrewAI (8)#Crypto (12)#Cryptocurrency (12)#Cryptography (8)#Custody (9)#DSPy (8)#Data (13)#Data Engineering (12)#Data Structures (9)#Databases (37)#Deployment (3)#Design Patterns (10)#DevOps (16)#DevSecOps (11)#Developer Experience (5)#Developer Tools (5)#Distributed Systems (94)#Documentation (3)#Edge AI (8)#Embeddings (15)#Emotional Intelligence (8)#Energy (8)#Engineering (11)#Engineering Culture (3)#Engineering Practices (16)#Error Handling (4)#Evaluation (53)#Event-Driven Architecture (8)#FREE-AI (8)#FX (5)#Feedback (4)#FinOps (23)#FinTech (6)#Financial AI (14)#Financial Systems (129)#Fine-Tuning (11)#Fintech (131)#Flutter (8)#Foreign Exchange (5)#Forward Deployed Engineer (8)#Forward Deployed Engineering (8)#Fraud (10)#Function Tools (5)#Functional Programming (3)#Fundraising (8)#GCP (5)#Gemma (4)#Generative AI (3)#Git (8)#Go (220)#Go-to-Market (8)#Google ADK (36)#Governance (56)#Granite (6)#GraphQL (3)#Growth (3)#Guardrails (25)#HIPAA (3)#HTTP (3)#Harness Engineering (8)#Hiring (8)#Hugging Face (8)#Human-in-the-Loop (8)#IBM watsonx (8)#Identity (11)#Integration (3)#Intellectual Property (8)#Interfaces (3)#JavaScript (8)#KYC (11)#KYC and AML (12)#Kafka (10)#Kubernetes (17)#LLM (5)#LLM Inference (8)#LLM-as-Judge (3)#LLMs (135)#LangChain (8)#LangGraph (11)#Leadership (26)#Ledger (12)#Legal (8)#Lending (14)#LlamaIndex (8)#MCP (22)#MLOps (31)#Machine Learning (32)#Marketing (16)#Markets (4)#Memory (15)#Memory Management (5)#Metrics (6)#Microservices (3)#Microsoft Agent Framework (150)#Middleware (6)#Migration (9)#Monitoring (3)#Multi-Agent (10)#Multi-Agent AI (14)#Multi-Agent Systems (73)#Multimodal (3)#Multimodal AI (8)#NIM (5)#NVIDIA (8)#OAuth (3)#OWASP (7)#Observability (44)#On-Device AI (8)#Open Source (7)#OpenTelemetry (5)#Operating Systems (8)#Operations (10)#Opinion (6)#Orchestration (10)#Organizational Design (8)#Payment Rails (16)#Payments (54)#People (8)#Performance (43)#Platform Engineering (9)#PreSales (8)#Privacy (5)#Privacy Engineering (3)#Process (4)#Product (27)#Product Management (8)#Production (8)#Programming (10)#Programming Languages (48)#Prompt Engineering (66)#Prompt Injection (6)#Protocol Buffers (3)#Protocols (9)#Providers (4)#Pydantic AI (8)#Python (142)#Quality (3)#RAG (58)#RBI (3)#REST (5)#Rails (16)#Reasoning Models (8)#Reconciliation (3)#RegTech (8)#Regulation (9)#Reliability (48)#Resilience (4)#Responsible AI (5)#Retrieval (3)#Risk (13)#Rust (32)#SRE (21)#Sales (9)#Scalability (3)#Security (81)#Security Engineering (8)#Self-Evolving Agents (16)#Sessions (3)#Settlement (9)#Soft Skills (8)#Software (3)#Software Architecture (36)#Software Engineering (144)#Spanner (4)#Startups (30)#Strands (8)#Streaming (28)#Structured Output (4)#Sustainability (8)#System Design (32)#Systems Programming (48)#Testing (49)#Tool Use (22)#Tooling (4)#Tools (3)#Trading (8)#Treasury (6)#Type System (3)#Type Systems (11)#TypeScript (8)#Vector Databases (21)#Vector Search (11)#Venture Capital (8)#Version Control (8)#Web Development (6)#Workflows (14)#gRPC (13)#smolagents (8)
Pratik Dhanave · ·13 min read

The Architect's Soft Skills and Leadership

The finale of "The Software Architect's Path" — why the non-technical skills decide whether a good design ever ships, and how communication, influence, mentoring, and humility turn a diagram into a system a whole team actually builds.

The capstone: the non-technical skills that make or break an architect — communication tailored to the audience, influence without authority, leading technically while staying hands-on, mentoring, and avoiding the ivory tower.

#Software Architecture#Leadership#Communication#Career
Pratik Dhanave · ·6 min read

Building Trust and Communication with Customers

An FDE's code only matters if the customer trusts them enough to adopt it — the relationship is not soft-skills garnish, it's the delivery mechanism.

An FDE's code only lands if the customer trusts them: earning trust in small kept promises, speaking the customer's outcomes and vocabulary, managing expectations relentlessly, navigating the org (champion/skeptic), and delivering bad news well.

#Forward Deployed Engineer#Communication#Trust#Consulting#Forward Deployed Engineering
Pratik Dhanave · ·13 min read

Giving Feedback That Lands

How to write code-review comments that improve the code and the relationship at the same time — commenting on the code not the coder, labeling severity so the author knows what blocks, asking instead of decreeing, teaching the why, and knowing when a thread belongs on a call.

Writing review comments that improve the code and the relationship: comment on the code not the coder, be specific and actionable, label severity (nit/suggestion/blocking), ask questions when you lack context, and pick your battles.

#Code Review#Communication#Feedback#Collaboration#Engineering Practices
Pratik Dhanave · ·8 min read

Influence and Social Skill

Being right is not enough to change anything. Every engineer has watched a worse idea win because its advocate was more persuasive, more trusted, or simply better at bringing people along — and concluded, wrongly, that this is unfair politics they want no part of. But influence isn't manipulation; it's the skill of helping good ideas actually happen through other people. In any organization, your impact is bounded not by the quality of your ideas but by your ability to get others to understand, trust, and act on them.

Being right is not enough to change anything. Every engineer has watched a worse idea win because its advocate was more persuasive or trusted. But influence isn't manipulation — it's the skill of helping good ideas actually happen through other people, and your impact is bounded by it.

#Emotional Intelligence#Influence#Leadership#Communication#Soft Skills
Pratik Dhanave · ·8 min read

Difficult Conversations and Feedback

The conversations we most want to avoid are usually the ones that matter most — telling a colleague their work isn't good enough, raising a concern with your manager, addressing a conflict that's festering, giving feedback that might not be welcome. Avoiding them feels safer in the moment and is almost always worse over time: problems grow, resentment builds, and the unsaid thing poisons the working relationship. Emotional intelligence doesn't make hard conversations easy, but it makes them possible to have well — which is a learnable skill that changes everything downstream.

The conversations we most want to avoid are usually the ones that matter most — telling a colleague their work isn't good enough, addressing a festering conflict, giving unwelcome feedback. EQ doesn't make hard conversations easy, but it makes them possible to have well — a learnable skill that changes everything downstream.

#Emotional Intelligence#Communication#Feedback#Leadership#Soft Skills
Pratik Dhanave · ·7 min read

Empathy: Understanding Others

Empathy is where emotional intelligence turns outward — and where it becomes genuinely useful to everyone around you. It's the difference between an engineer who "wins" a design debate by being loudest and one who understands what each person actually needs and finds a solution everyone supports; between a code review that makes someone defensive and one that helps them. Empathy isn't sentiment. It's the practical skill of accurately understanding what other people think and feel, and it's the foundation of every effective interaction.

Empathy is where emotional intelligence turns outward — and where it becomes genuinely useful to everyone around you. It isn't sentiment; it's the practical, learnable skill of accurately understanding what other people think and feel, and it's the foundation of every effective interaction.

#Emotional Intelligence#Empathy#Soft Skills#Communication#Leadership
Pratik Dhanave · ·8 min read

Objections and Negotiation

An objection feels like a rejection — the customer pushing back, resisting, saying no. The mental shift that transforms selling is realizing an objection is usually the opposite: a sign of engagement, a real concern surfaced, an invitation to address the thing standing between them and yes. Handled with the pushy-sales playbook (overcome it, pressure through it), objections end deals. Handled with genuine understanding, they're how deals get closed — by resolving the real concerns that were always going to decide the outcome.

An objection feels like a rejection — the customer pushing back. The mental shift that transforms selling is realizing it's usually the opposite: a sign of engagement, a real concern surfaced, an invitation to address the thing standing between them and yes. Handled with genuine understanding, objections are how deals get closed.

#Sales#PreSales#Negotiation#Communication#Business Strategy
Pratik Dhanave · ·8 min read

Discovery and Qualification

The instinct of every enthusiastic builder in a sales conversation is to talk — to explain the product, demo the features, make the case. It's almost always the wrong move. The best salespeople do the opposite: they ask, and they listen. Discovery (understanding the customer's actual problem) and qualification (determining whether they're even a real fit) are the unglamorous early stages where good selling is truly won or lost — and where an engineer's diagnostic instincts, properly aimed, are a genuine advantage.

The instinct of every enthusiastic builder in a sales conversation is to talk. It's almost always the wrong move. The best salespeople ask and listen. Discovery (understanding the customer's actual problem) and qualification (whether they're even a real fit) are where good selling is truly won — and where an engineer's diagnostic instincts are an advantage.

#Sales#PreSales#Business Strategy#Communication

All posts on this site are written by Pratik Dhanave, an Agentic AI Architect with 7+ years building production distributed systems, multi-agent AI platforms, and cloud-native infrastructure. About the author → Each article includes working code, architecture diagrams, and references to the specific frameworks and standards discussed. Browse all posts or explore related topics using the tag cloud above.